the link in Step 3 that points to info about Automated data classification is broken.

Hi team, this needs to be updated to include banned password not being compatible in GCC tenants. The note in the banned password doc is not clear that Gcc is not supported. Our team had to spend many days on the phone with MSFT to confirm this was not an option in Gcc.

https://docs.microsoft.com/en-us/azure/active-directory/authentication/howto-password-ban-bad-on-premises-faq

Bottom link on page:

https://docs.microsoft.com/en-us/enterprise-mobility-security/solutions/ems-govt-service-description#ems-offers-for-us-government-and-office-365-interoperability

claims to lead to Microsoft 365 Government but actually leads to main commercial EMS page.

https://docs.microsoft.com/enterprise-mobility-security/

Is the below link intended?

https://www.microsoft.com/en-US/microsoft-365/government

Given the product rollout cadence between Commercial and GCC/GCCH/DoD national clouds, it may be worth mentioning a few additional AIP unified labeling "gotchas" -

1.) As of writing, it is currently not possible to create custom sensitive information types in the Microsoft 365 Security & Compliance Center using the GUI referenced here, this is only available via the PowerShell methods referenced here.

2.) As of writing, there are substantially more Microsoft published SITs in Commercial tenants (~152) than GCCH tenants (~100).