Skip to content

Update credential prompts for clarity on roles#1868

Open
harrisaoz wants to merge 1 commit intoMicrosoftDocs:mainfrom
harrisaoz:patch-1
Open

Update credential prompts for clarity on roles#1868
harrisaoz wants to merge 1 commit intoMicrosoftDocs:mainfrom
harrisaoz:patch-1

Conversation

@harrisaoz
Copy link
Copy Markdown

Parameter description for: Get-Credential -Message (CloudCredential parameter of Set-AzureADKerberosServer)

Issue

The documentation currently states:
“An Active Directory user who is a member of the Hybrid Identity Administrators group for Microsoft Entra ID.”

This wording is inaccurate and misleading. Hybrid Identity Administrator is a Microsoft Entra ID role, not an on‑premises Active Directory group. The CloudCredential used with Set-AzureADKerberosServer must represent a Microsoft Entra ID account, and its permissions are evaluated in the cloud, not through AD DS group membership.

Recommended Correction

Replace the sentence with the following:
“A Microsoft Entra ID user who is assigned the Hybrid Identity Administrator role.”

Rationale

The CloudCredential parameter requires authentication to Microsoft Entra ID endpoints, which means the credential must be an Entra ID identity, not an AD DS account (even if the user happens to also exist on-prem). Role assignment for Hybrid Identity Administrator occurs in Entra ID, not in on‑prem Active Directory. This wording aligns with how permissions for Entra Kerberos server object creation are actually evaluated.

Parameter description for: Get-Credential -Message (CloudCredential parameter of Set-AzureADKerberosServer)
Issue:
The documentation currently states:

“An Active Directory user who is a member of the Hybrid Identity Administrators group for Microsoft Entra ID.”

This wording is inaccurate and misleading. Hybrid Identity Administrator is a Microsoft Entra ID role, not an on‑premises Active Directory group. The CloudCredential used with Set-AzureADKerberosServer must represent a Microsoft Entra ID account, and its permissions are evaluated in the cloud, not through AD DS group membership.
Recommended Correction:
Replace the sentence with the following:

“A Microsoft Entra ID user who is assigned the Hybrid Identity Administrator role.”

Rationale:

The CloudCredential parameter requires authentication to Microsoft Entra ID endpoints, which means the credential must be an Entra ID identity, not an AD DS account (even if the user happens to also exist on-prem).
Role assignment for Hybrid Identity Administrator occurs in Entra ID, not in on‑prem Active Directory.
This wording aligns with how permissions for Entra Kerberos server object creation are actually evaluated.
@prmerger-automator
Copy link
Copy Markdown
Contributor

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

@learn-build-service-prod
Copy link
Copy Markdown
Contributor

Learn Build status updates of commit fce806f:

✅ Validation status: passed

File Status Preview URL Details
docs/identity/authentication/howto-authentication-passwordless-security-key-on-premises.md ✅Succeeded

For more details, please refer to the build report.

Copy link
Copy Markdown
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 updates the credential prompt documentation for the Set-AzureADKerberosServer command to accurately reflect that the Hybrid Identity Administrator is a Microsoft Entra ID role, not an on-premises Active Directory group.

Changes:

  • Corrects the description of the cloud credential requirement to specify it must be a Microsoft Entra ID user with the Hybrid Identity Administrator role assigned
  • Updates both the code comment and the Get-Credential prompt message for consistency

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@Court72
Copy link
Copy Markdown
Contributor

Court72 commented Jan 23, 2026

@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

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.

4 participants