In our previous post, we introduced the private preview of Safe Key Rotation, a feature that helps Azure Cosmos DB customers avoid service disruptions during key rotations. By showing when each account key was last used, it helps teams make informed decisions before rotating keys or moving to Entra ID.
This capability addresses a common challenge: keys that appear unused may still support critical applications, which can lead to unexpected outages if they are rotated too soon.
What is new?
With public preview, we are expanding this capability to give you even more control and confidence when managing your account keys.
- Azure Cosmos DB now provides visibility into the last usage timestamp for each key, helping you understand when a key was last used before taking action.
- Safe key rotation can now be enabled directly from the Features blade, making it easy to adopt this capability.
- With active enablement, you can safely regenerate keys or disable local authentication with confidence, ensuring the key is no longer in use before making changes.
Get Started
Safe Key Rotation is now available to help you manage your account keys. Enable it in the Azure portal or explore the Safe Key Rotation documentation to learn more.
About Azure Cosmos DB
Azure Cosmos DB is a fully managed and serverless NoSQL and vector database for modern app development, including AI applications. With its SLA-backed speed and availability as well as instant dynamic scalability, it is ideal for real-time NoSQL and MongoDB applications that require high performance and distributed computing over massive volumes of NoSQL and vector data.
To stay in the loop on Azure Cosmos DB updates, follow us on X, YouTube, and LinkedIn. Join the discussion with other developers on the #nosql channel on the Microsoft Open Source Discord.
0 comments
Be the first to start the discussion.