Skip to content

Commit 05466e8

Browse files
authored
Merge pull request #103730 from localden/patch-1
Update with timeline alignment
2 parents 4816be5 + 3867fc2 commit 05466e8

File tree

1 file changed

+12
-10
lines changed

1 file changed

+12
-10
lines changed

articles/active-directory/fundamentals/whats-new.md

Lines changed: 12 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -223,31 +223,33 @@ For listing your application in the Azure AD app gallery, please read the detail
223223

224224
### ADAL End of Support Announcement
225225

226-
227-
228226
**Type:** N/A
229227
**Service category:** Other
230228
**Product capability:** Developer Experience
231229

232-
As part of our ongoing initiative to improve the developer experience, service reliability, and security of customer applications, we will end support for the Azure Active Directory Authentication Library (ADAL). The final deadline to migrate your applications to Microsoft Authentication Library (MSAL) has been extended to **June 1, 2023**.
230+
As part of our ongoing initiative to improve the developer experience, service reliability, and security of customer applications, we will end support for the Azure Active Directory Authentication Library (ADAL). The final deadline to migrate your applications to Microsoft Authentication Library (MSAL) has been extended to **June 30, 2023**.
231+
232+
### Why are we doing this?
233233

234-
### Why are we doing this?
235234
As we consolidate and evolve the Microsoft Identity platform, we are also investing in making significant improvements to the developer experience and service features that make it possible to build secure, robust and resilient applications. To make these features available to our customers we needed to update the architecture of our software development kits. As a result of this change, we’ve decided that the path forward requires us to sunset ADAL so that we can focus on developer experience investments with MSAL.
236235

237-
### What happens?
238-
We recognize that changing libraries is not an easy task, and cannot be accomplished quickly. We are committed to helping customers plan their migrations to MSAL as well as execute them with minimal disruption.
236+
### What happens?
237+
238+
We recognize that changing libraries is not an easy task, and cannot be accomplished quickly. We are committed to helping customers plan their migrations to MSAL as well as execute them with minimal disruption.
239+
239240
- In June 2020 we [announced the 2-year end of support timeline for ADAL](https://devblogs.microsoft.com/microsoft365dev/end-of-support-timelines-for-azure-ad-authentication-library-adal-and-azure-ad-graph/).
240241
- In December 2022 we’ve decided to extend the ADAL end of support to June 2023.
241242
- Through the next six months (January 2023 – June 2023) we will continue informing customers about the upcoming end of support along with providing guidance on migration.
242243
- On June 2023 we will officially sunset ADAL, removing library documentation and archiving all GitHub repositories related to the project.
243244

244-
### How to find out which applications in my tenant are using ADAL?
245+
### How to find out which applications in my tenant are using ADAL?
245246

246247
Refer to our post on [Microsoft Q&A](/answers/questions/360928/information-how-to-find-apps-using-adal-in-your-te.html) for details on identifying ADAL apps with the help of [Azure Workbooks](/azure/azure-monitor/visualize/workbooks-overview).
247-
### If I’m using ADAL, what can I expect after the deadline?
248+
### If I’m using ADAL, what can I expect after the deadline?
249+
248250
- There will be no new releases (security or otherwise) to the library after June 2023.
249-
- We will not be accepting any incident reports or support requests for ADAL. ADAL to MSAL Migration support would continue.
250-
- The underpinning services will continue working and applications that depend on ADAL should continue working; however, applications will be at increased security and reliability risk due to not having the latest updates, service configuration, and enhancements made available through the Microsoft Identity platform.
251+
- We will not be accepting any incident reports or support requests for ADAL. ADAL to MSAL migration support would continue.
252+
- The underpinning services will continue working and applications that depend on ADAL should continue working; however, applications and the resources they access will be at increased security and reliability risk due to not having the latest updates, service configuration, and enhancements made available through the Microsoft Identity platform.
251253

252254
### What features can I only access with MSAL?
253255

0 commit comments

Comments
 (0)