News

Azure AD Certificate Rollovers Get Delayed

Microsoft was told by businesses that more time was needed to prepare for the rollover.

• By Kurt Mackie
• 05/24/2016

It will be several more weeks before security certificates for Azure Active Directory are available, owing to "trust" issues.

Applications that tap certain federation metadata could experience trust issues from Microsoft's certificate rollover, especially those apps that are "not configured to automatically update the certificate from the metadata," Microsoft warned, in a terse announcement posted earlier this month. However, this week, Microsoft indicated it was holding off on the planned certificate rollover by "a few weeks."

Organizations told Microsoft that they needed more time to get ready.

Microsoft rolls out new security certificates for Azure Active Directory on a six-week schedule, although it could switch them out even earlier in an emergency. They're part of a public-private key pair design used to ensure trust between Azure Active Directory and Web applications.

Microsoft's best practices document on this topic indicates that organizations should build business logic into their applications to handle these kinds of regular certificate rollovers.

If a Web app was built using Microsoft's code samples, then they'll likely already have this logic built into them. "If you created your application using any of the code samples or walkthrough documentation provided by Microsoft, the key rollover logic is already included in your project," Microsoft's best practices document explains. Otherwise, the latest key has to be manually retrieved and updated in an application.

Applications in the Azure Active Directory application gallery that were configured to use SAML or WS-Federation protocols won't be adversely affected by the certificate rollover, the announcement explained.

Organizations experiencing problems with their Web apps as a result of Microsoft's certificate update should seek support at this page, Microsoft indicated.