Skip to content

Commit 39f16b5

Browse files
authored
Merge pull request #17175 from MicrosoftDocs/repo_sync_working_branch
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-stack-docs (branch main)
2 parents f48e9f3 + 97dd322 commit 39f16b5

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

azure-stack/operator/graph-api-retirement.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn how to mitigate the retirement of the Entra ID Graph API.
44
author: sethmanheim
55
ms.author: sethm
66
ms.topic: conceptual
7-
ms.date: 02/05/2025
7+
ms.date: 02/25/2025
88
ms.reviewer: rtiberiu
99

1010
---
@@ -15,7 +15,7 @@ The Microsoft Entra ID (formerly Azure Active Directory or Azure AD) [Graph API
1515

1616
## Mitigation steps
1717

18-
The Graph API retirement affects all Azure Stack Hub customers that use Entra ID as the identity provider, and requires you to run the script included in this article for all impacted applications. If you have applications that need continued access to the Graph APIs, the script sets a flag that configures these applications for an extension that allows these specific applications to continue calling the legacy Graph API until June 2025.
18+
The Graph API retirement affects all Azure Stack Hub customers that use Entra ID as the identity provider, and requires you to run the script included in this article for all impacted applications. If you have applications that need continued access to the Graph APIs, the script sets a flag that configures these applications for an extension that allows these specific applications to continue calling the legacy Graph API.
1919

2020
The PowerShell script provided in this article sets a flag for each application to configure the Graph API extension for each Entra ID identity provider of Azure Stack Hub.
2121

0 commit comments

Comments
 (0)