Skip to content

Conversation

@MartinM85
Copy link
Contributor

Important

Required for API changes:

  • [] Link to API.md file: ADD LINK HERE
  • [] Link to PR for public-facing schema changes (schema-Prod-beta/v1.0.csdl): ADD LINK HERE

Add other supporting information, such as a description of the PR changes:

The PR fixes unintended references to the beta version of the API in the documentation for the v1.0 API. It also removes one beta disclaimer mentioned in the documentation for the v1.0 API.

Similar fixes were delivered previously. These are the remaining occurrences.


Important

The following guidance is for Microsoft employees only. Community contributors can ignore this message; our content team will manage the status.

After you've created your PR, expand this section for tips and additional instructions.
  • do not merge is the default PR status and is automatically added to all open PRs that don't have the ready to merge label.
  • Add the ready for content review label to start a review. Only PRs that have met the minimum requirements for content review and have this label are reviewed.
  • If your content reviewer requests changes, review the feedback and address accordingly as soon as possible to keep your pull request moving forward. After you address the feedback, remove the changes requested label, add the review feedback addressed label, and select the Re-request review icon next to the content reviewer's alias. If you can't add labels, add a comment with #feedback-addressed to the pull request.
  • After the content review is complete, your reviewer will add the content review complete label. When the updates in this PR are ready for external customers to use, replace the do not merge label with ready to merge and the PR will be merged within 24 working hours.
  • Pull requests that are inactive for more than 6 weeks will be automatically closed. Before that, you receive reminders at 2 weeks, 4 weeks, and 6 weeks. If you still need the PR, you can reopen or recreate the request.

For more information, see the Content review process summary.

@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit 7f73c8f:

✅ Validation status: passed

File Status Preview URL Details
api-reference/v1.0/api/conditionalaccessroot-list-authenticationcontextclassreferences.md ✅Succeeded
api-reference/v1.0/api/crosstenantaccesspolicyconfigurationpartner-update.md ✅Succeeded
api-reference/v1.0/api/entitlementmanagement-post-connectedorganizations.md ✅Succeeded
api-reference/v1.0/api/externalconnectors-externalitem-get.md ✅Succeeded
api-reference/v1.0/api/filestoragecontainer-update.md ✅Succeeded
api-reference/v1.0/api/identityuserflowattributeassignment-delete.md ✅Succeeded
api-reference/v1.0/api/identityuserflowattributeassignment-getorder.md ✅Succeeded
api-reference/v1.0/api/learningprovider-list-learningcontents.md ✅Succeeded
api-reference/v1.0/api/licensedetails-getteamslicensingdetails.md ✅Succeeded
api-reference/v1.0/api/messagerule-get.md ✅Succeeded
api-reference/v1.0/api/onauthenticationmethodloadstartexternalusersselfservicesignup-post-identityproviders.md ✅Succeeded
api-reference/v1.0/api/onpremisesdirectorysynchronization-get.md ✅Succeeded
api-reference/v1.0/api/reportroot-getteamsteamcounts.md ✅Succeeded
api-reference/v1.0/api/riskyserviceprincipal-get.md ✅Succeeded
api-reference/v1.0/api/serviceprincipal-get.md ✅Succeeded
api-reference/v1.0/api/sharepointmigrationjob-list-progressevents.md ✅Succeeded
api-reference/v1.0/api/synchronization-synchronizationjob-post-bulkupload.md ✅Succeeded
api-reference/v1.0/api/team-sendactivitynotification.md ✅Succeeded
api-reference/v1.0/api/teamwork-get.md ✅Succeeded
api-reference/v1.0/api/temporaryaccesspassauthenticationmethodconfiguration-get.md ✅Succeeded
api-reference/v1.0/api/todotask-update.md ✅Succeeded
api-reference/v1.0/api/unifiedrolemanagementpolicyassignment-get.md ✅Succeeded
api-reference/v1.0/api/user-post-approleassignments.md ✅Succeeded
api-reference/v1.0/api/userflowlanguagepage-delete.md ✅Succeeded
api-reference/v1.0/resources/azure-ad-auditlog-overview.md ✅Succeeded

This comment lists only the first 25 files in the pull request.
For more details, please refer to the build report.

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR corrects version inconsistencies in v1.0 API documentation by fixing unintended references to the beta API version. These are cleanup changes that ensure the v1.0 documentation consistently uses v1.0 endpoints, metadata contexts, and include paths.

Key Changes

  • Updated example URLs from beta to v1.0 endpoints across 15 API documentation files
  • Fixed @odata.context metadata references from beta to v1.0 in response examples across 13 files
  • Corrected an include path from beta to v1.0 directory structure
  • Removed an inappropriate beta disclaimer from v1.0 documentation

Reviewed changes

Copilot reviewed 28 out of 28 changed files in this pull request and generated no comments.

Show a summary per file
File Description
security-retentioneventtype.md Fixed documentation link to reference v1.0 instead of beta retention label resource
intune-enrollment-conceptual.md Removed beta API disclaimer that doesn't apply to v1.0 documentation
fieldvalueset.md Updated example URL from beta to v1.0 endpoint
azure-ad-auditlog-overview.md Fixed sign-ins audit logs example URL to use v1.0
userflowlanguagepage-delete.md Updated request example URL to v1.0
user-post-approleassignments.md Fixed @odata.context in response from beta to v1.0
unifiedrolemanagementpolicyassignment-get.md Updated request example URL to v1.0
todotask-update.md Fixed @odata.context in response from beta to v1.0
temporaryaccesspassauthenticationmethodconfiguration-get.md Fixed @odata.context in response from beta to v1.0
teamwork-get.md Fixed @odata.context in response from beta to v1.0
team-sendactivitynotification.md Updated entity URL in request body to v1.0
synchronization-synchronizationjob-post-bulkupload.md Fixed location header URLs in three response examples from beta to v1.0
sharepointmigrationjob-list-progressevents.md Updated request example URL to v1.0
serviceprincipal-get.md Fixed @odata.context in response from beta to v1.0
riskyserviceprincipal-get.md Corrected include path from beta to v1.0 directory
reportroot-getteamsteamcounts.md Updated request example URL to v1.0
onpremisesdirectorysynchronization-get.md Fixed @odata.context in response from beta to v1.0
onauthenticationmethodloadstartexternalusersselfservicesignup-post-identityproviders.md Updated both request URL and @odata.id in request body to v1.0
messagerule-get.md Fixed @odata.context in response from beta to v1.0
licensedetails-getteamslicensingdetails.md Updated request URL and @odata.context in response to v1.0
learningprovider-list-learningcontents.md Fixed both @odata.context and @odata.nextLink in response to v1.0
identityuserflowattributeassignment-getorder.md Fixed @odata.context in response from beta to v1.0
identityuserflowattributeassignment-delete.md Updated request example URL to v1.0
filestoragecontainer-update.md Updated request example URL to v1.0
externalconnectors-externalitem-get.md Updated request example URL to v1.0
entitlementmanagement-post-connectedorganizations.md Updated request URL and @odata.context in response to v1.0
crosstenantaccesspolicyconfigurationpartner-update.md Updated request example URL to v1.0
conditionalaccessroot-list-authenticationcontextclassreferences.md Fixed @odata.context in response from beta to v1.0

@FaithOmbongi FaithOmbongi self-assigned this Dec 19, 2025
@FaithOmbongi FaithOmbongi added the ready to merge Use this label to indicate to the repository admins that your PR is ready to merge into master. label Dec 19, 2025
@FaithOmbongi FaithOmbongi merged commit 7b7e300 into microsoftgraph:main Dec 19, 2025
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ready to merge Use this label to indicate to the repository admins that your PR is ready to merge into master.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants