The following doc walks through various options and process of assessment and rotation of keyCredentials (certificates) for applications and service principal objects (Apps/SPs) created by services such as Azure Automation, Azure Migrate, Azure Site Recovery. Applications created via other mechanisms might need to rotate their credentials if your tenant admin identified a credential on your application as needing attention.

Azure AD application needing credential rotation could have been created by Azure Automation Service, Azure Migrate Service, Azure Site Recovery or manually using the Azure portal. To pick the right remediation guidance, you must pick the assessment script for the one of these services. If one or more of these services are used in your organization, you will need to run through the assessment script for each of the services. This will ensure you are able to pick the right guidance and avoid downtime for your app/service. The following table can help identify the type of service that created the Azure AD application.

Guidance in these documents applies only in relation to the mitigation steps necessary for the issue disclosed in the CVE and detailed in Microsoft Security Response Center blog. Do not use this guidance as general credential rotation procedure.

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.

This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.