[BULK] - DocuTune remediation - Sensitive terms with GUIDs

[meganbradley]

Applying sensitive terms with GUID changes as part of Content SFI and outlined in Overview - Writing content securely - Platform Manual. Changes are part of the Microsoft-wide SFI effort. Point of contact: @CelesteDG

DocuTune v1.5.2.0
CorrelationId: ac15aa43-4e2b-437f-ab1c-fdd7e79cd4db

#docutune

---

Internal previews

📄 File	🔗 Preview link
aspnetcore/blazor/security/blazor-web-app-with-entra.md	Secure an ASP.NET Core Blazor Web App with Microsoft Entra ID
aspnetcore/blazor/security/blazor-web-app-with-oidc.md	Secure an ASP.NET Core Blazor Web App with OpenID Connect (OIDC)
aspnetcore/blazor/security/webassembly/hosted-with-azure-active-directory-b2c.md	Secure a hosted ASP.NET Core Blazor WebAssembly app with Azure Active Directory B2C
aspnetcore/blazor/security/webassembly/hosted-with-microsoft-entra-id.md	aspnetcore/blazor/security/webassembly/hosted-with-microsoft-entra-id
aspnetcore/blazor/security/webassembly/standalone-with-azure-active-directory-b2c.md	Secure an ASP.NET Core Blazor WebAssembly standalone app with Azure Active Directory B2C
aspnetcore/blazor/security/webassembly/standalone-with-microsoft-accounts.md	Secure an ASP.NET Core Blazor WebAssembly standalone app with Microsoft Accounts
aspnetcore/blazor/security/webassembly/standalone-with-microsoft-entra-id.md	Secure an ASP.NET Core Blazor WebAssembly standalone app with Microsoft Entra ID

[meganbradley]

#docutune-review

[guardrex]

Thanks @meganbradley. Note that the Content SFI guidance/initiative is internal. I'm a contractor without access to the resources for this effort, nor was I informed by anyone that these changes are required. I'll sweep the rest of the Blazor node in this doc set for similar use of GUIDs to update.