Skip to content

Entra ID replacements and clearer wording of token #25

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 7 commits into
base: main
Choose a base branch
from

Conversation

erwinkramer
Copy link

  1. Use EntraId throughout the documentation instead of AzureAd.
  2. Microsoft Entra Identity isn't a product name as far as i know, it's Microsoft Entra ID, replaced all occurrences.
  3. Clearer "X-MS-API-ROLE request header" paragraph. I used the wording "access token's roles claim" and "access token" instead of just "token", because those are used in other parts of the documentation as well.

Copy link
Contributor

@erwinkramer : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

Copy link
Contributor

Learn Build status updates of commit 2c283fd:

✅ Validation status: passed

File Status Preview URL Details
data-api-builder/authentication-azure.md ✅Succeeded
data-api-builder/authorization.md ✅Succeeded
data-api-builder/overview.md ✅Succeeded
data-api-builder/reference-command-line-interface.md ✅Succeeded
data-api-builder/reference-configuration.md ✅Succeeded
data-api-builder/TOC.yml ✅Succeeded
data-api-builder/whats-new/version-0.md ✅Succeeded
data-api-builder/whats-new/version-1-5.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

Copy link
Contributor

PRMerger Results

Issue Description
Yaml File(s) This PR includes changes to .yml file(s) owned by another author.

@v-regandowner
Copy link
Contributor

@JerryNixon @seesharprun - Can you review the proposed changes?

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator bot added the aq-pr-triaged tracking label for the PR review team label May 16, 2025
@v-dirichards
Copy link
Contributor

@seesharprun @JerryNixon Could you review this proposed update to your article and enter #sign-off in a comment if it's ready to merge?

Thanks!

Copy link
Contributor

Learn Build status updates of commit a8fb8dc:

✅ Validation status: passed

File Status Preview URL Details
data-api-builder/authentication-azure.md ✅Succeeded
data-api-builder/authorization.md ✅Succeeded
data-api-builder/overview.md ✅Succeeded
data-api-builder/reference-command-line-interface.md ✅Succeeded
data-api-builder/reference-configuration.md ✅Succeeded
data-api-builder/TOC.yml ✅Succeeded
data-api-builder/whats-new/version-0.md ✅Succeeded
data-api-builder/whats-new/version-1-5.md ✅Succeeded

For more details, please refer to the build report.

Copy link
Contributor

PRMerger Results

Issue Description
Yaml File(s) This PR includes changes to .yml file(s) owned by another author.

@v-dirichards
Copy link
Contributor

@seesharprun

Can you review this old PR and determine whether it needs to be closed or merged?

@MicrosoftDocs/public-repo-pr-review-team

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants