Update Azure Active Directoy, Azure AD, and AAD baseline references to Microsoft Entra ID equivalent

ahuynhMITRE commented 1 week ago

🗣 Description

Updated Azure Activie Directoy, Azure AD, AAD references in the markdown files including unique IDs and references in other baselines to match the renaming of the M365 product.

💭 Motivation and context

This change is required in order to be up to date with how Microsoft references their products. Microsoft renamed Azure Active Directory (Azure AD) to Microsoft Entra ID to communicate the multicloud, multiplatform functionality of the products, alleviate confusion with Windows Server Active Directory, and unify the Microsoft Entra product family.

Closes issue #888 linked to #921

🧪 Testing

check each instance of Azure Active Directoy, Azure AD, and AAD mentioned in the baselines are correctly replaced with their Microsoft Entra equivalent

✅ Pre-approval checklist

[x] This PR has an informative and human-readable title.
[x] PR targets the correct parent branch (e.g., main or release-name) for merge.
[x] Changes are limited to a single goal - eschew scope creep!
[x] Changes are sized such that they do not touch excessive number of files.
[x] All future TODOs are captured in issues, which are referenced in code comments.
[x] These code changes follow the ScubaGear content style guide.
[x] Related issues these changes resolve are linked preferably via closing keywords.
[x] All relevant type-of-change labels added.
[x] All relevant project fields are set.
[x] All relevant repo and/or project documentation updated to reflect these changes.
[x] Unit tests added/updated to cover PowerShell and Rego changes.
[x] Functional tests added/updated to cover PowerShell and Rego changes.
[x] All relevant functional tests passed.
[x] All automated checks (e.g., linting, static analysis, unit/smoke tests) passed.

✅ Pre-merge checklist

[ ] PR passed smoke test check.
[ ] Feature branch has been rebased against changes from parent branch, as needed

Use Rebase branch button below or use this reference to rebase from the command line.
[ ] Resolved all merge conflicts on branch
[ ] Notified merge coordinator that PR is ready for merge via comment mention

✅ Post-merge checklist

[ ] Feature branch deleted after merge to clean up repository.
[ ] Verified that all checks pass on parent branch (e.g., main or release-name) after merge.

ahuynhMITRE commented 1 week ago

@buidav & @mitchelbaker-cisa for the unique IDs i originally changed MS.AAD to MS.ENTRAID but looking at Microsoft's documentation their prefered acronym replacement for AAD is ME-ID...

Link listed below. https://learn.microsoft.com/en-us/entra/fundamentals/new-name

open to changing it to ENTRAID to match the markdown file name and also not sure if the "-" breaks our automation for pulling unique IDs.

buidav commented 1 week ago

@buidav & @mitchelbaker-cisa for the unique IDs i originally changed MS.AAD to MS.ENTRAID but looking at Microsoft's documentation their prefered acronym replacement for AAD is ME-ID...

Link listed below. https://learn.microsoft.com/en-us/entra/fundamentals/new-name

open to changing it to ENTRAID to match the markdown file name and also not sure if the "-" breaks our automation for pulling unique IDs.

We will have to think about the strategy and bumping major versions for i.e v1 to v2 for ScubaGear itself when changing the IDs now. This is a breaking change that will interrupt current workflows for folks.

buidav commented 4 days ago

@ahuynhMITRE For when you get back. Would recommend reverting the Policy identifiers back to MS.AAD for this PR. We'll have to make identifiers changes in a separate PR in the future. Changing the policy identifiers now would be too disruptive of current workflows.

cisagov / ScubaGear