đź“‹ Microsoft Entra Documentation Changes

Daily summary for changes since September 25th 2025, 7:59 PM PDT

Report generated on September 26th 2025, 7:59 PM PDT

📊 Summary

17
Total Commits
0
New Files
4
Modified Files
0
Deleted Files
11
Contributors

📝 Modified Documentation Files

+14 / -7 lines changed
Commit: Add screenshots and one more limitation.
Changes:
Before
After
 
1. Navigate to **Global Secure Access** > **Settings** > **Session management** > **Custom Block Page**
2. Switch **Custom body message** to **On**.
3. Configure the Customized body message you would prefer.
4. (Optional) Paste one or multiple clickable links via limited markdown language (for example `[click here](https://bing.com)`).
5. Preview the customized message with the **Preview** button.
6. Select **Save** to save the custom block page.
 
 
## Notes and limitations
 
- The Custom body message is limited to 1024 Unicode (utf-8) characters.
- Changes to a custom block page might take a few minutes to propagate to active sessions.
- Custom block pages appear for TLS inspected traffic only.
- Ensure any contact information you publish complies with your organization's privacy policies.
 
## Verify the block page
 
1. From a device with the Global Secure Access client installed and the Internet Access traffic forwarding profile enabled, attempt to navigate to a site that your policy blocks.
2. Observe the block experience and confirm the custom messaging displays.
 
1. Navigate to **Global Secure Access** > **Settings** > **Session management** > **Custom Block Page**
2. Switch **Custom body message** to **On**.
3. Configure the Customized body message you would prefer. For example, ``.
4. (Optional) Paste one or multiple clickable links via limited markdown language (for example, `[click here](https://bing.com)`).
5. Preview the customized message with the **Preview** button.
6. Select **Save** to save the custom block page.
 
![Screenshot showing the preview experience in the admin portal](media/how-to-customize-block-page/custom-block-preview.png)
 
> [!NOTE]
> A known transient issue in public preview could result in this save failing. While Microsoft team works on a fix, the current mitigation is to re-configure the custom block page and try again.
 
## Verify the block page
 
1. From a device with the Global Secure Access client installed and the Internet Access traffic forwarding profile enabled, attempt to navigate to a site that your policy blocks.
2. Observe the block experience and confirm the custom messaging displays.
 
![Screenshot showing end user experience of the custom block page](media/how-to-customize-block-page/custom-block.png)
 
+1 / -1 lines changed
Commit: Specify role requirement for signing into Entra admin center
Changes:
Before
After
 
Protected actions use a Conditional Access authentication context, so you must configure an authentication context and add it to a Conditional Access policy. If you already have a policy with an authentication context, you can skip to the next section.
 
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com).
 
1. Select **Entra ID** > **Conditional Access** > **Authentication context** > **Authentication context**.
 
 
Protected actions use a Conditional Access authentication context, so you must configure an authentication context and add it to a Conditional Access policy. If you already have a policy with an authentication context, you can skip to the next section.
 
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Conditional Access Administrator](../role-based-access-control/permissions-reference.md#conditional-access-administrator).
 
1. Select **Entra ID** > **Conditional Access** > **Authentication context** > **Authentication context**.
 
+1 / -1 lines changed
Commit: Update PRT lifetime to 90 days
Changes:
Before
After
 
| Token Type | Issued by | Purpose | Scoped to Resource | Lifetime | Revocable | Renewable |
|------|------|------|------|------|------|------|
| Primary Refresh Token (PRT)| Entra ID | Request Access Tokens | No – Can request an access token for any resource | 14 days\*| Yes | Yes|
| Refresh Token| Entra ID| Request Access Tokens | Yes | 90 days\* | Yes | Yes |
| Access Token | Entra ID | Access the resource | Yes | Variable 60-90 minutes| Yes, if CAE capable | No |
| App auth cookie| Web app | Access the resource | Yes | Determined by application| Depends on application | No |
 
| Token Type | Issued by | Purpose | Scoped to Resource | Lifetime | Revocable | Renewable |
|------|------|------|------|------|------|------|
| Primary Refresh Token (PRT)| Entra ID | Request Access Tokens | No – Can request an access token for any resource | 90 days\*| Yes | Yes|
| Refresh Token| Entra ID| Request Access Tokens | Yes | 90 days\* | Yes | Yes |
| Access Token | Entra ID | Access the resource | Yes | Variable 60-90 minutes| Yes, if CAE capable | No |
| App auth cookie| Web app | Access the resource | Yes | Determined by application| Depends on application | No |
Modified by Alexander Filipin on Sep 26, 2025 4:14 PM
đź“– View on learn.microsoft.com
+1 / -1 lines changed
Commit: adjust SCU prediction
Changes:
Before
After
## Prerequisites
- You must have [Microsoft Entra ID Governance or Microsoft Entra Suite licenses](licensing-fundamentals.md).
- You must [Onboard to Security Copilot](/copilot/security/get-started-security-copilot#onboarding-to-security-copilot) with at least one [security compute unit (SCU)](/copilot/security/manage-usage) provisioned.
- Completing an access review that includes 20 decisions consumes on average one SCU. This includes the agent gathering insights and generating recommendations and the reviewer's natural language conversation in Microsoft Teams with the agent. The SCU consumption can vary based on the conversation length between the reviewer and agent.
- Admins must have at least **all** the following roles to set up and manage the agent in the Microsoft Entra admin center:
- [Identity Governance Administrator](../identity/role-based-access-control/permissions-reference.md#identity-governance-administrator)
- [Lifecycle Workflows Administrator](../identity/role-based-access-control/permissions-reference.md#lifecycle-workflows-administrator)
## Prerequisites
- You must have [Microsoft Entra ID Governance or Microsoft Entra Suite licenses](licensing-fundamentals.md).
- You must [Onboard to Security Copilot](/copilot/security/get-started-security-copilot#onboarding-to-security-copilot) with at least one [security compute unit (SCU)](/copilot/security/manage-usage) provisioned.
- Completing an access review that includes 20 decisions consumes on average 4.5 SCU. This includes the agent gathering insights and generating recommendations and the reviewer's natural language conversation in Microsoft Teams with the agent. The SCU consumption can vary based on the conversation length between the reviewer and agent.
- Admins must have at least **all** the following roles to set up and manage the agent in the Microsoft Entra admin center:
- [Identity Governance Administrator](../identity/role-based-access-control/permissions-reference.md#identity-governance-administrator)
- [Lifecycle Workflows Administrator](../identity/role-based-access-control/permissions-reference.md#lifecycle-workflows-administrator)