feat: add friendlyNameOverride and fix ids value#8
Merged
adutto-coreview merged 1 commit intoJul 3, 2026
Conversation
agardini-coreview
approved these changes
Jul 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Improves baseline readability for operators and aligns Authentication Methods Policy configuration identifiers with Microsoft Graph API casing.
Changes
$friendlyNameOverride(CIS M365 Foundations 6.0.1)Added display-name overrides for three user resources whose default friendly names would be unclear in baseline views:
break-glass@${TenantDomainName}emergency-access@${TenantDomainName}admin@${TenantDomainName}These overrides are display-only and do not affect resource content, logical identifiers, or deployment behavior.
Authentication Method Configuration
idcasingCorrected the
idfield in sevenAuthenticationMethodConfigurationscontent files to use PascalCase, matching Microsoft Graph API values:email→Emailfido2→Fido2microsoftAuthenticator→MicrosoftAuthenticatorsms→SmstemporaryAccessPass→TemporaryAccessPassvoice→Voicex509Certificate→X509CertificateAreas to review
idvalues match live Graph API responses forauthenticationMethodsPolicy/authenticationMethodConfigurations. If any consumers keyed off the previous camelCase values, this could affect resource matching or drift detection."Parent - Child"style).$friendlyNameOverrideentries; Essential 8 baselines were not modified in this PR.