📋 Microsoft Entra Documentation Changes

Daily summary for changes since August 27th 2025, 8:08 PM PDT

Report generated on August 28th 2025, 8:08 PM PDT

📊 Summary

23
Total Commits
0
New Files
6
Modified Files
0
Deleted Files
10
Contributors

📝 Modified Documentation Files

MODIFIED docs/global-secure-access/reference-points-of-presence.md
Modified by Ken Withee on Aug 28, 2025 4:18 PM
📖 View on learn.microsoft.com
+49 / -49 lines changed
Commit: Adds Azure Region.
Changes:
Before
After
### Asia Pacific (APAC)
The table lists the deployment status for the APAC region.
 
|Location | Global Secure Access service deployed | Remote network connectivity gateways |
| --- | --- | --- |
|Auckland, New Zealand | ✅ | |
|Busan, South Korea | ✅ | ✅ |
|Chennai, India | ✅ | ✅ |
|Melbourne, Australia | ✅ | ✅ |
|Osaka, Japan | ✅ | ✅ |
|Pune, India | ✅ | |
|Seoul, South Korea | ✅ | ✅ |
|Singapore, Singapore | ✅ | |
|Sydney, Australia | ✅ | ✅ |
|Taipei, Taiwan | ✅ | |
|Tokyo, Japan | ✅ | ✅ |
 
 
### Europe Middle East Africa (EMEA)
The table lists the deployment status for the EMEA region.
### Asia Pacific (APAC)
The table lists the deployment status for the APAC region.
 
| Azure Region | Physical Location | Global Secure Access service deployed | Remote network connectivity gateways |
| --- | --- | --- | --- |
| New Zealand North | Auckland, New Zealand | ✅ | |
| Korea South | Busan, South Korea | ✅ | ✅ |
| South India | Chennai, India | ✅ | ✅ |
| Australia Southeast | Melbourne, Australia | ✅ | ✅ |
| Japan West | Osaka, Japan | ✅ | ✅ |
| Central India | Pune, India | ✅ | |
| Korea Central | Seoul, South Korea | ✅ | ✅ |
| Southeast Asia | Singapore, Singapore | ✅ | |
| Australia East | Sydney, Australia | ✅ | ✅ |
| Taiwan North | Taipei, Taiwan | ✅ | |
| Japan East | Tokyo, Japan | ✅ | ✅ |
 
 
### Europe Middle East Africa (EMEA)
The table lists the deployment status for the EMEA region.
MODIFIED docs/fundamentals/how-to-find-tenant.md
Modified by Jill Grant on Aug 28, 2025 7:48 PM
📖 View on learn.microsoft.com
+2 / -2 lines changed
Commit: Apply suggestions from code review
Changes:
Before
After
 
2. Browse to **Entra ID** > **Overview** > **Properties**.
 
:::image type="content" source="media/how-to-find-tenant/identity-overview-properties.png" alt-text="Microsoft Entra ID - Identity Properties overview":::
 
3. Scroll down to the **Tenant ID** section and you can find your tenant ID in the box.
 
 
3. Scroll down to the **Tenant ID** section and you can find your tenant ID in the box.
 
:::image type="content" source="media/how-to-find-tenant/portal-tenant-id.png" alt-text="Microsoft Entra ID - Properties - Tenant ID - Tenant ID field":::
<!-- docutune:enable -->
 
## Find tenant ID with PowerShell
 
2. Browse to **Entra ID** > **Overview** > **Properties**.
 
:::image type="content" source="media/how-to-find-tenant/identity-overview-properties.png" alt-text="Screenshot of Microsoft Entra ID - Identity Properties overview.":::
 
3. Scroll down to the **Tenant ID** section and you can find your tenant ID in the box.
 
 
3. Scroll down to the **Tenant ID** section and you can find your tenant ID in the box.
 
:::image type="content" source="media/how-to-find-tenant/portal-tenant-id.png" alt-text="Screenshot of Microsoft Entra ID - Properties - Tenant ID - Tenant ID field.":::
<!-- docutune:enable -->
 
## Find tenant ID with PowerShell
MODIFIED docs/identity/authentication/concept-authentication-external-method-provider.md
Modified by emakedon23 on Aug 28, 2025 6:54 PM
📖 View on learn.microsoft.com
+2 / -2 lines changed
Commit: Update OIDC Discovery URL and issuer example
Changes:
Before
After
 
 
```json
http://customcaserver.azurewebsites.net/v2.0/.well-known/openid-configuration
{
"authorization_endpoint": "https://customcaserver.azurewebsites.net/api/Authorize",
"claims_supported": [
"id_token_signing_alg_values_supported": [
"RS256"
],
"issuer": "https://customcaserver.azurewebsites.net",
"jwks_uri": "http://customcaserver.azurewebsites.net/.well-known/jwks",
"response_modes_supported": [
"form_post"
 
 
```json
https://customcaserver.azurewebsites.net/v2.0/.well-known/openid-configuration
{
"authorization_endpoint": "https://customcaserver.azurewebsites.net/api/Authorize",
"claims_supported": [
"id_token_signing_alg_values_supported": [
"RS256"
],
"issuer": "https://customcaserver.azurewebsites.net/v2.0",
"jwks_uri": "http://customcaserver.azurewebsites.net/.well-known/jwks",
"response_modes_supported": [
"form_post"
MODIFIED docs/fundamentals/configure-security.md
Modified by John Flores on Aug 28, 2025 2:17 PM
📖 View on learn.microsoft.com
+3 / -0 lines changed
Commit: [Fundamentals] Securing Entra Updates
Changes:
Before
After
 
## Protect engineering systems
 
### Global Administrator role activation triggers an approval workflow
[!INCLUDE [21817](../includes/secure-recommendations/21817.md)]
 
 
 
 
 
## Protect engineering systems
 
### Cloud-only emergency access accounts exist
[!INCLUDE [21835](../includes/secure-recommendations/21835.md)]
 
### Global Administrator role activation triggers an approval workflow
[!INCLUDE [21817](../includes/secure-recommendations/21817.md)]
 
MODIFIED docs/architecture/gsa-poc-private-access.md
Modified by Janice Ricketts on Aug 28, 2025 8:49 PM
📖 View on learn.microsoft.com
+1 / -1 lines changed
Commit: Remove 'the' from sentence about Entra Private Access
Changes:
Before
After
 
### Coexist with a partner
 
When customers deploy the 3P solution, they might want to use the Microsoft Entra Private Access while using other solutions for internet access. For guidance, see [Partner ecosystem overview](../global-secure-access/partner-ecosystems-overview.md).
 
## Troubleshoot
 
 
### Coexist with a partner
 
When customers deploy the 3P solution, they might want to use Microsoft Entra Private Access while using other solutions for internet access. For guidance, see [Partner ecosystem overview](../global-secure-access/partner-ecosystems-overview.md).
 
## Troubleshoot
 
MODIFIED docs/includes/secure-recommendations/21835.md
Modified by John Flores on Aug 28, 2025 2:17 PM
📖 View on learn.microsoft.com
+1 / -0 lines changed
Commit: [Fundamentals] Securing Entra Updates
Changes:
Before
After
# risklevel: High
# userimpact: Low
# implementationcost: High
---
Microsoft recommends that organizations have two cloud-only emergency access accounts permanently assigned the [Global Administrator](/entra/identity/role-based-access-control/permissions-reference#global-administrator) role. These accounts are highly privileged and aren't assigned to specific individuals. The accounts are limited to emergency or "break glass" scenarios where normal accounts can't be used or all other administrators are accidentally locked out.
 
 
# risklevel: High
# userimpact: Low
# implementationcost: High
# Copied from \docs\includes\definitions\emergency-access-accounts.md
---
Microsoft recommends that organizations have two cloud-only emergency access accounts permanently assigned the [Global Administrator](/entra/identity/role-based-access-control/permissions-reference#global-administrator) role. These accounts are highly privileged and aren't assigned to specific individuals. The accounts are limited to emergency or "break glass" scenarios where normal accounts can't be used or all other administrators are accidentally locked out.
 

🤖 This report was automatically generated by the Entra Docs Monitor

📧 Delivered to [email protected]

🔗 Visit Repository