📋 Microsoft Entra Documentation Changes

Changes for May 13th 2025

Period: May 12th 2025, 12:00 AM to May 13th 2025, 12:00 AM

📚 Historical Report: This report shows documentation changes that occurred during the 24-hour period ending on May 13th 2025.

📊 Summary

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

📝 Modified Documentation Files

MODIFIED docs/identity-platform/scenario-spa-acquire-token.md
Modified by OwenRichards1 on May 12, 2025 10:45 PM
📖 View on learn.microsoft.com
+94 / -222 lines changed
Commit: update-acquire-token
Changes:
Before
After
description: Learn how to acquire a token in a single-page app and call a web API using the Microsoft identity platform.
author: henrymbuguakiarie
manager: CelesteDG
ms.author: henrymbugua
ms.date: 04/10/2025
ms.service: identity-platform
ms.topic: how-to
ms.reviewer: negoe
The choice between a pop-up or redirect experience depends on your application flow:
 
- If you don't want users to move away from your main application page during authentication, we recommend the pop-up method. Because the authentication redirect happens in a pop-up window, the state of the main application is preserved.
 
- If users have browser constraints or policies where pop-up windows are disabled, you can use the redirect method. Use the redirect method with the Internet Explorer browser, because there are [known issues with pop-up windows on Internet Explorer](msal-js-known-issues-ie-edge-browsers.md).
 
You can set the API scopes that you want the access token to include when it's building the access token request. All requested scopes might not be granted in the access token. That depends on the user's consent.
 
## Acquire a token with a pop-up window
 
# [JavaScript (MSAL.js v2)](#tab/javascript2)
 
description: Learn how to acquire a token in a single-page app and call a web API using the Microsoft identity platform.
author: henrymbuguakiarie
manager: CelesteDG
ms.author: OwenRichards1
ms.date: 05/12/2025
ms.service: identity-platform
ms.topic: how-to
ms.reviewer: negoe
The choice between a pop-up or redirect experience depends on your application flow:
 
- If you don't want users to move away from your main application page during authentication, we recommend the pop-up method. Because the authentication redirect happens in a pop-up window, the state of the main application is preserved.
- If users have browser constraints or policies where pop-up windows are disabled, you can use the redirect method. Use the redirect method with the Internet Explorer browser, because there are [known issues with pop-up windows on Internet Explorer](msal-js-known-issues-ie-edge-browsers.md).
 
You can set the API scopes that you want the access token to include when it's building the access token request. All requested scopes might not be granted in the access token. That depends on the user's consent.
 
## Acquire a token with a pop-up window
 
# [React](#tab/react)
 
The following code combines the previously described pattern with the methods for a pop-up experience:
MODIFIED docs/identity-platform/scenario-spa-sign-in.md
Modified by OwenRichards1 on May 12, 2025 10:13 PM
📖 View on learn.microsoft.com
+125 / -125 lines changed
Commit: adjusting sign in and sign out doc
Changes:
Before
After
---
title: Single-page app sign-in & sign-out
description: Learn how to build a single-page application (sign-in)
author: OwenRichards1
manager: CelesteDG
ms.author: owenrichards
ms.custom:
ms.date: 04/30/2022
ms.service: identity-platform
 
ms.topic: how-to
#Customer intent: As an application developer, I want to know how to write a single-page application by using the Microsoft identity platform.
---
 
# Single-page application: sign-in and sign-out
 
[!INCLUDE [applies-to-workforce-only](../external-id/includes/applies-to-workforce-only.md)]
 
The choice between a pop-up or redirect experience depends on your application flow.
 
---
title: Single-page app sign-in & sign-out code
description: Learn how to build a single-page application (sign-in)
author: OwenRichards1
manager: CelesteDG
ms.author: owenrichards
ms.custom:
ms.date: 05/12/2025
ms.service: identity-platform
 
ms.topic: how-to
#Customer intent: As an application developer, I want to know how to write a single-page application by using the Microsoft identity platform.
---
 
# Single-page application: Add sign-in and sign-out code
 
[!INCLUDE [applies-to-workforce-only](../external-id/includes/applies-to-workforce-only.md)]
 
The choice between a pop-up or redirect experience depends on your application flow.
 
MODIFIED docs/identity-platform/scenario-spa-app-configuration.md
Modified by OwenRichards1 on May 12, 2025 9:41 PM
📖 View on learn.microsoft.com
+30 / -58 lines changed
Commit: removing-versions-for-spas
Changes:
Before
After
manager: CelesteDG
ms.author: owenrichards
ms.custom:
ms.date: 02/11/2020
ms.service: identity-platform
 
ms.topic: how-to
 
# Single-page application: Code configuration
 
 
[!INCLUDE [applies-to-workforce-only](../external-id/includes/applies-to-workforce-only.md)]
 
Learn how to configure the code for your single-page application (SPA).
 
[!INCLUDE [active-directory-develop-libraries-spa](./includes/libraries/libraries-spa.md)]
 
## Application code configuration
 
In an MSAL library, the application registration information is passed as configuration during the library initialization.
manager: CelesteDG
ms.author: owenrichards
ms.custom:
ms.date: 05/12/2025
ms.service: identity-platform
 
ms.topic: how-to
 
# Single-page application: Code configuration
 
[!INCLUDE [applies-to-workforce-only](../external-id/includes/applies-to-workforce-only.md)]
 
Learn how to configure the code for your single-page application (SPA).
 
[!INCLUDE [active-directory-develop-libraries-spa](./includes/libraries/libraries-spa.md)]
 
## Prerequisites
 
* Register a new app in the [Microsoft Entra admin center](https://entra.microsoft.com), configured for *Accounts in this organizational directory only*. Refer to [Register an application](quickstart-register-app.md) for more details. Record the following values from the application **Overview** page for later use:
* Application (client) ID
MODIFIED docs/identity-platform/msal-js-initializing-client-applications.md
Modified by OwenRichards1 on May 12, 2025 8:33 PM
📖 View on learn.microsoft.com
+10 / -12 lines changed
Commit: clear-up-refs
Changes:
Before
After
manager: CelesteDG
ms.author: owenrichards
ms.custom:
ms.date: 02/27/2024
ms.reviewer: saeeda
ms.service: identity-platform
 
ms.topic: how-to
 
## Prerequisites
 
Before initializing an application, you first need to [register it in the Microsoft Entra admin center](scenario-spa-app-registration.md), establishing a trust relationship between your application and the Microsoft identity platform.
 
After registering your app, you'll need some or all of the following values that can be found in the Microsoft Entra admin center.
 
| Value | Required | Description |
| :---------------------- | :------: | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Application (client) ID | Required | A GUID that uniquely identifies your application within the Microsoft identity platform. |
| Authority | Optional | The identity provider URL (the *instance*) and the *sign-in audience* for your application. The instance and sign-in audience, when concatenated, make up the *authority*. |
| Directory (tenant) ID | Optional | Specify Directory (tenant) ID if you're building a line-of-business application solely for your organization, often referred to as a *single-tenant application*. |
manager: CelesteDG
ms.author: owenrichards
ms.custom:
ms.date: 05/12/2025
ms.reviewer:
ms.service: identity-platform
 
ms.topic: how-to
 
## Prerequisites
 
Before initializing an application, you first need to [register it in the Microsoft Entra admin center](scenario-spa-app-configuration), establishing a trust relationship between your application and the Microsoft identity platform.
 
After registering your app, you'll need some or all of the following values that can be found in the Microsoft Entra admin center.
 
| Value | Required | Description |
| :---- | :------: | :---- |
| Application (client) ID | Required | A GUID that uniquely identifies your application within the Microsoft identity platform. |
| Authority | Optional | The identity provider URL (the *instance*) and the *sign-in audience* for your application. The instance and sign-in audience, when concatenated, make up the *authority*. |
| Directory (tenant) ID | Optional | Specify Directory (tenant) ID if you're building a line-of-business application solely for your organization, often referred to as a *single-tenant application*. |
MODIFIED docs/identity-platform/msal-authentication-flows.md
Modified by OwenRichards1 on May 12, 2025 8:33 PM
📖 View on learn.microsoft.com
+9 / -9 lines changed
Commit: clear-up-refs
Changes:
Before
After
 
The Microsoft Authentication Library (MSAL) supports several authorization grants and associated token flows for use by different application types and scenarios.
 
| Authentication flow | Enables | Supported application types |
|-----------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| [Authorization code](#authorization-code) | User sign-in and access to web APIs on behalf of the user. | [Desktop](scenario-desktop-app-registration.md) <br /> [Mobile](scenario-mobile-app-registration.md) <br /> [Single-page app (SPA)](scenario-spa-app-registration.md) (requires PKCE) <br /> [Web](scenario-web-api-call-api-app-registration.md) |
| [Client credentials](#client-credentials) | Access to web APIs by using the identity of the application itself. Typically used for server-to-server communication and automated scripts requiring no user interaction. | [Daemon](scenario-daemon-app-registration.md) |
| [Device code](#device-code) | User sign-in and access to web APIs on behalf of the user on input-constrained devices like smart TVs and IoT devices. Also used by command line interface (CLI) applications. | [Desktop, Mobile](scenario-desktop-acquire-token-device-code-flow.md) |
| [Implicit grant](#implicit-grant) | User sign-in and access to web APIs on behalf of the user. *Do not use this flow - use authorization code with PKCE instead.* | * [Single-page app (SPA)](scenario-spa-app-registration.md) <br /> * [Web](scenario-web-api-call-api-app-registration.md)
| [On-behalf-of (OBO)](#on-behalf-of-obo) | Access from an "upstream" web API to a "downstream" web API on behalf of the user. The user's identity and delegated permissions are passed through to the downstream API from the upstream API. | [Web API](scenario-web-api-call-api-app-registration.md) |
| [Username/password (ROPC)](#usernamepassword-ropc) | Allows an application to sign in the user by directly handling their password. *Do not use this flow.* | [Desktop, Mobile](scenario-desktop-acquire-token-username-password.md)
| [Integrated Windows authentication (IWA)](#integrated-windows-authentication-iwa) | Allows applications on domain or Microsoft Entra joined computers to acquire a token silently (without any UI interaction from the user). | [Desktop, Mobile](scenario-desktop-acquire-token-integrated-windows-authentication.md) |
 
## Tokens
 
 
The Microsoft Authentication Library (MSAL) supports several authorization grants and associated token flows for use by different application types and scenarios.
 
| Authentication flow | Enable | Supported application types |
|----|----|----|
| [Authorization code](#authorization-code) | User sign-in and access to web APIs on behalf of the user. | [Desktop](scenario-desktop-app-registration.md) <br /> [Mobile](scenario-mobile-app-registration.md) <br /> [Single-page app (SPA)](scenario-spa-app-configuration) (requires PKCE) <br /> [Web](scenario-web-api-call-api-app-registration.md) |
| [Client credentials](#client-credentials) | Access to web APIs by using the identity of the application itself. Typically used for server-to-server communication and automated scripts requiring no user interaction. | [Daemon](scenario-daemon-app-registration.md) |
| [Device code](#device-code) | User sign-in and access to web APIs on behalf of the user on input-constrained devices like smart TVs and IoT devices. Also used by command line interface (CLI) applications. | [Desktop, Mobile](scenario-desktop-acquire-token-device-code-flow.md) |
| [Implicit grant](#implicit-grant) | User sign-in and access to web APIs on behalf of the user. *Do not use this flow - use authorization code with PKCE instead.* | * [Single-page app (SPA)](scenario-spa-app-configuration) <br /> * [Web](scenario-web-api-call-api-app-registration.md)
| [On-behalf-of (OBO)](#on-behalf-of-obo) | Access from an "upstream" web API to a "downstream" web API on behalf of the user. The user's identity and delegated permissions are passed through to the downstream API from the upstream API. | [Web API](scenario-web-api-call-api-app-registration.md) |
| [Username/password (ROPC)](#usernamepassword-ropc) | Allows an application to sign in the user by directly handling their password. *Do not use this flow.* | [Desktop, Mobile](scenario-desktop-acquire-token-username-password.md) |
| [Integrated Windows authentication (IWA)](#integrated-windows-authentication-iwa) | Allows applications on domain or Microsoft Entra joined computers to acquire a token silently (without any UI interaction from the user). | [Desktop, Mobile](scenario-desktop-acquire-token-integrated-windows-authentication.md) |
 
## Tokens
 
MODIFIED docs/identity-platform/includes/libraries/libraries-spa.md
Modified by OwenRichards1 on May 12, 2025 9:41 PM
📖 View on learn.microsoft.com
+5 / -11 lines changed
Commit: removing-versions-for-spas
Changes:
Before
After
manager: CelesteDG
---
 
| Language / framework | Project on<br/>GitHub | Package | Getting<br/>started | Sign in users | Access web APIs | Generally available (GA) _or_<br/>Public preview<sup>1</sup> |
| -------------------- | ---------------------- | ------- | :--------------------: | :-----------: | :-------------: | :----------------------------------------------------------: |
| Angular | [MSAL Angular v2](https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/dev/lib/msal-angular)<sup>2</sup> | [msal-angular](https://www.npmjs.com/package/@azure/msal-angular) | [Quickstart](../../quickstart-single-page-app-angular-sign-in.md) | ![Library can request ID tokens for user sign-in.][y] | ![Library can request access tokens for protected web APIs.][y] | GA |
| Angular | [MSAL Angular](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/msal-angular-v1/lib/msal-angular)<sup>3</sup> | [msal-angular](https://www.npmjs.com/package/@azure/msal-angular) | — | ![Library can request ID tokens for user sign-in.][y] | ![Library can request access tokens for protected web APIs.][y] | GA |
| AngularJS | [MSAL AngularJS](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/dev/lib/msal-angular)<sup>3</sup> | [msal-angularjs](https://www.npmjs.com/package/@azure/msal-angular) | — | ![Library can request ID tokens for user sign-in.][y] | ![Library can request access tokens for protected web APIs.][y] | Public preview |
| JavaScript | [MSAL.js v2](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/dev/lib/msal-browser)<sup>2</sup> | [msal-browser](https://www.npmjs.com/package/@azure/msal-browser) | [Tutorial](../../tutorial-v2-javascript-auth-code.md) | ![Library can request ID tokens for user sign-in.][y] | ![Library can request access tokens for protected web APIs.][y] | GA |
| JavaScript | [MSAL.js 1.0](/javascript/api/overview/msal-overview)<sup>3</sup> | [msal-core](https://www.npmjs.com/package/@azure/msal-core) | — | ![Library can request ID tokens for user sign-in.][y] | ![Library can request access tokens for protected web APIs.][y] | GA |
| React | [MSAL React](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/dev/lib/msal-react)<sup>2</sup> | [msal-react](https://www.npmjs.com/package/@azure/msal-react) | [Quickstart](../../quickstart-single-page-app-react-sign-in.md) | ![Library can request ID tokens for user sign-in.][y] | ![Library can request access tokens for protected web APIs.][y] | GA |
 
<!--
| Vue | [Vue MSAL](https://github.com/mvertopoulos/vue-msal) | [vue-msal](https://www.npmjs.com/package/vue-msal) | ![X indicating no.][n] | ![Green check mark.][y] | ![Green check mark.][y] | -- |
 
<sup>1</sup> [Universal License Terms for Online Services][preview-tos] apply to libraries in *Public preview*.
 
manager: CelesteDG
---
 
| Language / framework | Project on<br/>GitHub | Package | Getting<br/>started | Sign in users | Access web APIs |
| -------------------- | ---------------------- | ------- | :--------------------: | :-----------: | :-------------: |
| React | [MSAL React](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/dev/lib/msal-react)<sup>2</sup> | [msal-react](https://www.npmjs.com/package/@azure/msal-react) | [Quickstart](../../quickstart-single-page-app-sign-in.md) | ![Library can request ID tokens for user sign-in.][y] | ![Library can request access tokens for protected web APIs.][y] |
| JavaScript | [MSAL.js v2](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/dev/lib/msal-browser)<sup>2</sup> | [msal-browser](https://www.npmjs.com/package/@azure/msal-browser) | [Quickstart](../../quickstart-single-page-app-sign-in) | ![Library can request ID tokens for user sign-in.][y] | ![Library can request access tokens for protected web APIs.][y] |
| Angular | [MSAL Angular v2](https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/dev/lib/msal-angular)<sup>2</sup> | [msal-angular](https://www.npmjs.com/package/@azure/msal-angular) | [Quickstart](../../quickstart-single-page-app-sign-in) | ![Library can request ID tokens for user sign-in.][y] | ![Library can request access tokens for protected web APIs.][y] |
 
<sup>1</sup> [Universal License Terms for Online Services][preview-tos] apply to libraries in *Public preview*.
 
 
 
 
 
 
 
MODIFIED docs/identity-platform/migrate-spa-implicit-to-auth-code.md
Modified by OwenRichards1 on May 12, 2025 8:33 PM
📖 View on learn.microsoft.com
+6 / -8 lines changed
Commit: clear-up-refs
Changes:
Before
After
---
title: Migrate JavaScript single-page app from implicit grant to authorization code flow
description: How to update a JavaScript SPA using MSAL.js 1.x and the implicit grant flow to MSAL.js 2.x and the authorization code flow with PKCE and CORS support.
author: OwenRichards1
manager: CelesteDG
ms.author: owenrichards
ms.custom:
ms.date: 07/17/2020
ms.service: identity-platform
 
ms.topic: how-to
 
MSAL.js 2.x improves on MSAL.js 1.x by supporting the authorization code flow in the browser instead of the implicit grant flow. MSAL.js 2.x does **NOT** support the implicit flow.
 
## Migration steps
 
To update your application to MSAL.js 2.x and the auth code flow, there are three primary steps:
 
 
## Switch redirect URIs to SPA platform
---
title: Migrate JavaScript single-page app from implicit grant to authorization code flow
description: How to update a JavaScript SPA using MSAL.js 2.x and the authorization code flow with PKCE and CORS support.
author: OwenRichards1
manager: CelesteDG
ms.author: owenrichards
ms.custom:
ms.date: 05/12/2025
ms.service: identity-platform
 
ms.topic: how-to
 
MSAL.js 2.x improves on MSAL.js 1.x by supporting the authorization code flow in the browser instead of the implicit grant flow. MSAL.js 2.x does **NOT** support the implicit flow.
 
## Perform migration steps
 
To update your application to MSAL.js 2.x and the auth code flow, there are three primary steps:
 
 
## Switch redirect URIs to SPA platform
MODIFIED docs/identity-platform/tutorial-single-page-app-javascript-prepare-app.md
Modified by OwenRichards1 on May 12, 2025 8:33 PM
📖 View on learn.microsoft.com
+5 / -3 lines changed
Commit: clear-up-refs
Changes:
Before
After
 
## Create a JavaScript project and install dependencies
 
1. Open Visual Studio Code, select **File** > **Open Folder...**. Navigate to and select the location in which to create your project.
1. Open a new terminal by selecting **Terminal** > **New Terminal**.
1. Run the following command to create a new JavaScript project:
 
## Adding your tenant details to the MSAL configuration
 
The **authConfig.js** file contains the configuration settings for the authentication flow and is used to configure **MSAL.js** with the required settings for authentication.
 
### [Workforce tenant](#tab/workforce-tenant)
 
auth: {
clientId: "Enter_the_Application_Id_Here",
// WORKFORCE TENANT
authority: "https://login.microsoftonline.com/Enter_the_Tenant_Info_Here", // Replace the placeholder with your tenant info
redirectUri: '/', // You must register this URI on App Registration. Defaults to window.location.href e.g. http://localhost:3000/
navigateToLoginRequestUrl: true, // If "true", will navigate back to the original request location before processing the auth code response.
},
 
## Create a JavaScript project and install dependencies
 
1. Sign into the Microsoft Entra admin center as a Global Administrator.
1. Open Visual Studio Code, select **File** > **Open Folder...**. Navigate to and select the location in which to create your project.
1. Open a new terminal by selecting **Terminal** > **New Terminal**.
1. Run the following command to create a new JavaScript project:
 
## Adding your tenant details to the MSAL configuration
 
The **authConfig.js** file contains the configuration settings for the authentication flow and is used to configure **MSAL.js** with the required settings for authentication. Use your client secret of
 
### [Workforce tenant](#tab/workforce-tenant)
 
auth: {
clientId: "Enter_the_Application_Id_Here",
// WORKFORCE TENANT
authority: "https://login.microsoftonline.com/aaaabbbb-0000-cccc-1111-dddd2222eeee", // Replace the placeholder with your tenant info
redirectUri: '/', // You must register this URI on App Registration. Defaults to window.location.href e.g. http://localhost:3000/
navigateToLoginRequestUrl: true, // If "true", will navigate back to the original request location before processing the auth code response.
MODIFIED docs/identity-platform/v2-oauth2-auth-code-flow.md
Modified by OwenRichards1 on May 12, 2025 8:33 PM
📖 View on learn.microsoft.com
+2 / -2 lines changed
Commit: clear-up-refs
Changes:
Before
After
manager: CelesteDG
ms.author: owenrichards
ms.custom:
ms.date: 01/04/2025
ms.service: identity-platform
ms.reviewer: jmprieur, ludwignick
 
 
Redirect URIs for SPAs that use the auth code flow require special configuration.
 
- **Add a redirect URI** that supports auth code flow with PKCE and cross-origin resource sharing (CORS): Follow the steps in [Redirect URI: MSAL.js 2.0 with auth code flow](scenario-spa-app-registration.md#redirect-uri-msaljs-20-with-auth-code-flow).
- **Update a redirect URI**: Set the redirect URI's `type` to `spa` by using the [application manifest editor](reference-app-manifest.md) in the Microsoft Entra admin center.
 
The `spa` redirect type is backward-compatible with the implicit flow. Apps currently using the implicit flow to get tokens can move to the `spa` redirect URI type without issues and continue using the implicit flow. Despite this backward compatibility, we recommend that you use the auth code flow with PKCE for SPAs.
manager: CelesteDG
ms.author: owenrichards
ms.custom:
ms.date: 05/12/2025
ms.service: identity-platform
ms.reviewer: jmprieur, ludwignick
 
 
Redirect URIs for SPAs that use the auth code flow require special configuration.
 
- **Add a redirect URI** that supports auth code flow with PKCE and cross-origin resource sharing (CORS): Follow the steps in [How to add a redirect URI to your application](how-to-add-redirect-uri.md).
- **Update a redirect URI**: Set the redirect URI's `type` to `spa` by using the [application manifest editor](reference-app-manifest.md) in the Microsoft Entra admin center.
 
The `spa` redirect type is backward-compatible with the implicit flow. Apps currently using the implicit flow to get tokens can move to the `spa` redirect URI type without issues and continue using the implicit flow. Despite this backward compatibility, we recommend that you use the auth code flow with PKCE for SPAs.
MODIFIED docs/identity-platform/scenario-spa-call-api.md
Modified by OwenRichards1 on May 12, 2025 10:59 PM
📖 View on learn.microsoft.com
+1 / -2 lines changed
Commit: final-edit
Changes:
Before
After
manager: CelesteDG
ms.author: owenrichards
ms.custom:
ms.date: 11/25/2022
ms.service: identity-platform
 
ms.topic: how-to
## Next steps
 
- Learn more by building a React Single-page application (SPA) that signs in users in the following multi-part [tutorial series](tutorial-single-page-app-react-prepare-app.md).
 
- Explore Microsoft identity platform [single-page application code samples](sample-v2-code.md#single-page-applications)
manager: CelesteDG
ms.author: owenrichards
ms.custom:
ms.date: 05/12/2025
ms.service: identity-platform
 
ms.topic: how-to
## Next steps
 
- Learn more by building a React Single-page application (SPA) that signs in users in the following multi-part [tutorial series](tutorial-single-page-app-react-prepare-app.md).
- Explore Microsoft identity platform [single-page application code samples](sample-v2-code.md#single-page-applications)
 
MODIFIED docs/identity-platform/tutorial-single-page-app-react-prepare-app.md
Modified by OwenRichards1 on May 12, 2025 11:03 PM
📖 View on learn.microsoft.com
+1 / -1 lines changed
Commit: remove dummy value
Changes:
Before
After
author: OwenRichards1
manager: CelesteDG
ms.author: owenrichards
ms.date: 02/25/2025
ms.service: identity-platform
ms.topic: tutorial
#Customer intent: As a React developer, I want to know how to create a new React project in an IDE and add authentication.
author: OwenRichards1
manager: CelesteDG
ms.author: owenrichards
ms.date: 05/25/2025
ms.service: identity-platform
ms.topic: tutorial
#Customer intent: As a React developer, I want to know how to create a new React project in an IDE and add authentication.
MODIFIED docs/identity-platform/access-tokens.md
Modified by Owen Richards on May 12, 2025 7:44 PM
📖 View on learn.microsoft.com
+1 / -1 lines changed
Commit: Update access-tokens.md
Changes:
Before
After
 
Apply default token lifetime variation to organizations that have Continuous Access Evaluation (CAE) enabled. Apply default token lifetime variation even if the organizations use CTL policies. The default token lifetime for long lived token lifetime ranges from 20 to 28 hours. When the access token expires, the client must use the refresh token to silently acquire a new refresh token and access token.
 
Organizations that use [Conditional Access sign-in frequency (SIF)](~/identity/conditional-access/concept-session-lifetime.md#user-sign-in-frequency) to enforce how frequently sign-ins occur can't override default access token lifetime variation. When organizations use SIF, the time between credential prompts for a client is the token lifetime that ranges from 60 - 90 minutes plus the sign-in frequency interval.
 
Here's an example of how default token lifetime variation works with sign-in frequency. Let's say an organization sets sign-in frequency to occur every hour. When the token has lifetime ranging from 60-90 minutes due to token lifetime variation, the actual sign-in interval occurs anywhere between 1 hour to 2.5 hours.
 
 
Apply default token lifetime variation to organizations that have Continuous Access Evaluation (CAE) enabled. Apply default token lifetime variation even if the organizations use CTL policies. The default token lifetime for long lived token lifetime ranges from 20 to 28 hours. When the access token expires, the client must use the refresh token to silently acquire a new refresh token and access token.
 
Organizations that use [Conditional Access sign-in frequency (SIF)](~/identity/conditional-access/concept-session-lifetime.md#user-sign-in-frequency) to enforce how frequently sign-ins occur can't override default access token lifetime variation. When organizations use SIF, the time between credential prompts for a client can range from the sign-in frequency interval to the token lifetime that ranges from 60 - 90 minutes plus the sign-in frequency interval.
 
Here's an example of how default token lifetime variation works with sign-in frequency. Let's say an organization sets sign-in frequency to occur every hour. When the token has lifetime ranging from 60-90 minutes due to token lifetime variation, the actual sign-in interval occurs anywhere between 1 hour to 2.5 hours.
 
MODIFIED docs/identity/hybrid/install.md
Modified by ManoharLakkoju-MSFT on May 12, 2025 2:56 PM
📖 View on learn.microsoft.com
+1 / -0 lines changed
Commit: (AzureCXP) fixes MicrosoftDocs/Entra-docs#419673
Changes:
Before
After
Cloud sync uses the Microsoft Entra provisioning agent. Use the steps below to install it.
 
[!INCLUDE [sign in](~/includes/cloud-sync-sign-in.md)]
4. On the left, select **Agent**.
5. Select **Download on-premises agent**, and select **Accept terms & download**.
6. Once the **Microsoft Entra provisioning agent package** has completed downloading, run the *AADConnectProvisioningAgentSetup.exe* installation file from your downloads folder.
 
Cloud sync uses the Microsoft Entra provisioning agent. Use the steps below to install it.
 
[!INCLUDE [sign in](~/includes/cloud-sync-sign-in.md)]
3. Select **cloud sync**
4. On the left, select **Agent**.
5. Select **Download on-premises agent**, and select **Accept terms & download**.
6. Once the **Microsoft Entra provisioning agent package** has completed downloading, run the *AADConnectProvisioningAgentSetup.exe* installation file from your downloads folder.

🤖 This historical report was generated by the Entra Docs Monitor

🔗 Visit Repository

📅 ← Back to All Reports