Skip to content

Conversation

@TeeEarls
Copy link
Contributor

Clarified requirements for sync client version before applying SOA settings.

Clarified requirements for sync client version before applying SOA settings.
@prmerger-automator
Copy link
Contributor

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

@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit 92a6e2c:

✅ Validation status: passed

File Status Preview URL Details
docs/identity/hybrid/how-to-group-source-of-authority-configure.md ✅Succeeded

For more details, please refer to the build report.

@v-dirichards v-dirichards requested a review from Copilot October 16, 2025 21:13
@v-dirichards
Copy link
Contributor

@Justinha

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

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 clarifies the requirements for sync client versions when configuring Group Source of Authority (SOA). The change emphasizes that sync clients must be upgraded to supported versions before applying SOA settings to ensure proper handling.

  • Added clarification that sync client versions should be verified before applying SOA settings

Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.

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.

3 participants