Procedure and the consequence when Rotating the keyCredentials in Azure Active Directory?

EnterpriseArchitect 6,061 Reputation points
2023-11-16T13:50:03.26+00:00

Hi All,

I have received the email from Microsoft for the Action required: Rotate your keyCredentials in Azure Active Directory.

I wonder what the procedure and impact will be when executing it as we have an Azure production environment globally so it is running 24x7.

Any help would be greatly appreciated.

Azure Key Vault
Azure Key Vault
An Azure service that is used to manage and protect cryptographic keys and other secrets used by cloud apps and services.
1,453 questions
Microsoft Security | Microsoft Entra | Microsoft Entra External ID
Microsoft Security | Microsoft Entra | Microsoft Entra ID
Microsoft Security | Microsoft Entra | Other
{count} votes

Accepted answer
  1. Carlos Solís Salazar 18,201 Reputation points MVP Volunteer Moderator
    2023-11-16T16:58:52.4866667+00:00

    This process generally involves updating the credentials (like secrets or certificates) used by applications to authenticate with Azure AD. Here's a guide on how to proceed and what to consider, especially given that you have a global Azure production environment running 24x7:

    Procedure for Rotating KeyCredentials

    1. Identify Affected Applications

    • Determine which applications use the keyCredentials that need to be rotated. This could include applications that authenticate using Azure AD for various services.

    2. Generate New Credentials

    • Go to the Azure portal and navigate to the Azure Active Directory section.
    • Find the application registration(s) affected.
    • Under the "Certificates & secrets" tab, generate new client secrets or upload new certificates, as applicable.
    • Note down the new credentials securely.

    3. Update Applications with New Credentials

    • Update the applications with the new credentials. This step will vary depending on how each application is configured.
    • If possible, test the updated credentials in a staging or development environment before deploying them to production.

    4. Monitor Applications Post-Update

    • After updating the credentials in the applications, monitor them closely for any sign of issues or authentication failures.

    Impact and Considerations

    1. Minimizing Downtime

    • Plan the update during a maintenance window or low-traffic period if possible, to minimize impact.
    • Some modern applications can refresh their credentials without needing a restart, but this depends on how the application is designed.

    2. Backup Old Credentials

    • Keep the old credentials active while you make the transition to the new ones. This will allow for a fallback in case of any issues with the new credentials.

    3. Communication

    • Inform relevant stakeholders and teams about the planned changes and potential impacts.

    4. Testing

    • Ensure thorough testing in a non-production environment to validate that applications work correctly with the new credentials.

    5. Rollback Plan

    • Have a rollback plan in case you encounter unexpected issues during or after the update.

    6. Documentation

    • Update any documentation to reflect the changes made.

    7. Compliance and Auditing

    • Record the change for compliance and auditing purposes.

    8. Removing Old Credentials

    • Once you are confident that the new credentials are working as expected, remove the old credentials from Azure AD to maintain security.

    References

    By carefully planning and executing this process, you can rotate the keyCredentials with minimal impact on your production environment.

    Accept the answer if the information helped you. This will help us and others in the community as well.

    1 person found this answer helpful.

1 additional answer

Sort by: Most helpful
  1. Akshay-MSFT 17,961 Reputation points Microsoft Employee Moderator
    2023-11-23T11:34:21.2633333+00:00

    @EnterpriseArchitect

    As Answered in https://learn.microsoft.com/en-us/answers/questions/1432879/automating-the-certificates-or-client-secrets-rota?comment=question

    Currently we don't have an option to import or rotate certificate from Azure Key Vault for an Entra ID registered application, however we could use a federated credential from Key Vault.

    Using a Customer managed keys to encrypt data in your tenant using Azure Key Vault in another tenant. This could be done via a managed identity.

    User's image

    User's image

    User's image

    Once Setup, Now you could Navigate to your Keys in KeyVault and setup a rotation policy for the same:

    User's image

    Thanks,

    Akshay Kaushik

    Please "Accept the answer(Yes)" and "share you feedback ". This will help us and others in the community as well.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.