{"id":13173,"date":"2026-11-02T04:00:45","date_gmt":"2026-11-02T12:00:45","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/cosmosdb\/?p=13173"},"modified":"2026-10-30T09:18:18","modified_gmt":"2026-10-30T16:18:18","slug":"azure-cosmos-db-access-control-growing-teams","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/cosmosdb\/azure-cosmos-db-access-control-growing-teams\/","title":{"rendered":"My Team Is Growing, How Do I Structure Who Gets Access to What?"},"content":{"rendered":"<p><span data-contrast=\"auto\">Your project started with one or two people. Now developers, operators, analysts, and applications all need access to Azure Cosmos DB. Giving everyone the same permissions might feel efficient, but it makes every identity more powerful than its job requires.<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/p>\n<p><span data-contrast=\"auto\">As your team grows, organize access around jobs, not people. Separate management access from data access, assign roles to groups and workload identities, and use the smallest practical scope.<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><span data-contrast=\"auto\">You do not need a complicated permission model for every person. You need a small set of repeatable access patterns.<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/p>\n<p><div class=\"alert alert-info\">This article is focused on Azure Cosmos DB for NoSQL. Authentication and authorization options differ from other Azure Cosmos DB APIs.<\/div><\/p>\n<h3><span class=\"TextRun SCXW7634046 BCX8\" lang=\"EN-US\" xml:lang=\"EN-US\" data-contrast=\"none\"><span class=\"NormalTextRun SCXW7634046 BCX8\" data-ccp-parastyle=\"heading 2\">Separate managing the account from using its data<\/span><\/span><\/h3>\n<p><span data-contrast=\"auto\">Azure Cosmos DB access has two planes:<\/span><\/p>\n<ul>\n<li><span data-contrast=\"auto\">The <\/span><b><span data-contrast=\"auto\">control plane <\/span><\/b><span data-contrast=\"auto\">covers managing Azure resources: configuring the account, creating databases and containers, changing throughput, and managing role assignments. These permissions use Azure role-based access control (Azure RBAC).<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/li>\n<li><span data-contrast=\"auto\">The <\/span><b><span data-contrast=\"auto\">data plane <\/span><\/b><span data-contrast=\"auto\">covers working with items: reading, querying, creating, updating, and deleting data. Azure Cosmos DB for NoSQL provides its own native data-plane RBAC.<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/li>\n<\/ul>\n<p><span data-contrast=\"auto\">That distinction lets you separate jobs that are often combined. A platform engineer can manage account configuration without reading customer data. An application can read and write items without changing throughput or networking.<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><span data-contrast=\"auto\">Being an Azure <\/span><b><span data-contrast=\"auto\">Owner<\/span><\/b><span data-contrast=\"auto\">\u202for <\/span><b><span data-contrast=\"auto\">Contributor<\/span><\/b><span data-contrast=\"auto\">\u202fdoes not automatically grant item access. Similarly, a Cosmos DB data role does not grant permission to configure the account.<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/p>\n<p><a href=\"https:\/\/devblogs.microsoft.com\/cosmosdb\/wp-content\/uploads\/sites\/52\/2026\/11\/blog_note_overview.png\"><img decoding=\"async\" class=\"alignnone wp-image-13192 size-full\" src=\"https:\/\/devblogs.microsoft.com\/cosmosdb\/wp-content\/uploads\/sites\/52\/2026\/11\/blog_note_overview.png\" alt=\"Illustrated guide to managing Azure Cosmos DB access as teams grow. Recommends least privilege, roles assigned to groups and workload identities, and separating control plane resource management from data plane access.\" width=\"1024\" height=\"1024\" srcset=\"https:\/\/devblogs.microsoft.com\/cosmosdb\/wp-content\/uploads\/sites\/52\/2026\/11\/blog_note_overview.png 1024w, https:\/\/devblogs.microsoft.com\/cosmosdb\/wp-content\/uploads\/sites\/52\/2026\/11\/blog_note_overview-300x300.png 300w, https:\/\/devblogs.microsoft.com\/cosmosdb\/wp-content\/uploads\/sites\/52\/2026\/11\/blog_note_overview-150x150.png 150w, https:\/\/devblogs.microsoft.com\/cosmosdb\/wp-content\/uploads\/sites\/52\/2026\/11\/blog_note_overview-768x768.png 768w, https:\/\/devblogs.microsoft.com\/cosmosdb\/wp-content\/uploads\/sites\/52\/2026\/11\/blog_note_overview-24x24.png 24w, https:\/\/devblogs.microsoft.com\/cosmosdb\/wp-content\/uploads\/sites\/52\/2026\/11\/blog_note_overview-48x48.png 48w, https:\/\/devblogs.microsoft.com\/cosmosdb\/wp-content\/uploads\/sites\/52\/2026\/11\/blog_note_overview-96x96.png 96w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/a><\/p>\n<p>&nbsp;<\/p>\n<h3><span class=\"TextRun SCXW85324040 BCX8\" lang=\"EN-US\" xml:lang=\"EN-US\" data-contrast=\"none\"><span class=\"NormalTextRun SCXW85324040 BCX8\" data-ccp-parastyle=\"heading 2\">Start with a small role model<\/span><\/span><\/h3>\n<p><span class=\"NormalTextRun SCXW15284983 BCX8\">Do not create a custom role for every team member. <\/span><span class=\"NormalTextRun SCXW15284983 BCX8\">Start with the jobs your team <\/span><span class=\"NormalTextRun SCXW15284983 BCX8\">actually performs.<\/span><\/p>\n<table style=\"border-collapse: collapse; width: 64.3798%;\">\n<tbody>\n<tr>\n<td style=\"width: 14.7977%;\"><strong>Identity or group<\/strong><\/td>\n<td style=\"width: 22.7792%;\"><strong>What it needs<\/strong><\/td>\n<td style=\"width: 26.8029%;\"><strong>Starting point<\/strong><\/td>\n<\/tr>\n<tr>\n<td style=\"width: 14.7977%;\"><span class=\"TextRun SCXW193314892 BCX8\" lang=\"EN-US\" xml:lang=\"EN-US\" data-contrast=\"auto\"><span class=\"NormalTextRun SCXW193314892 BCX8\">Application developers<\/span><\/span><\/td>\n<td style=\"width: 22.7792%;\"><span class=\"TextRun SCXW244875383 BCX8\" lang=\"EN-US\" xml:lang=\"EN-US\" data-contrast=\"auto\"><span class=\"NormalTextRun SCXW244875383 BCX8\">Build and test features<\/span><\/span><span class=\"EOP Selected SCXW244875383 BCX8\" data-ccp-props=\"{}\">\u00a0<\/span><\/td>\n<td style=\"width: 26.8029%;\"><span class=\"TextRun SCXW144686724 BCX8\" lang=\"EN-US\" xml:lang=\"EN-US\" data-contrast=\"auto\"><span class=\"NormalTextRun SCXW144686724 BCX8\">Data Contributor in nonproduction<\/span><\/span><\/td>\n<\/tr>\n<tr>\n<td style=\"width: 14.7977%;\"><span class=\"TextRun SCXW232170053 BCX8\" lang=\"EN-US\" xml:lang=\"EN-US\" data-contrast=\"auto\"><span class=\"NormalTextRun SCXW232170053 BCX8\">Production application<\/span><\/span><span class=\"EOP Selected SCXW232170053 BCX8\" data-ccp-props=\"{}\">\u00a0<\/span><\/td>\n<td style=\"width: 22.7792%;\"><span class=\"TextRun SCXW61614438 BCX8\" lang=\"EN-US\" xml:lang=\"EN-US\" data-contrast=\"auto\"><span class=\"NormalTextRun SCXW61614438 BCX8\">Serve one workload<\/span><\/span><span class=\"EOP Selected SCXW61614438 BCX8\" data-ccp-props=\"{}\">\u00a0<\/span><\/td>\n<td style=\"width: 26.8029%;\"><span class=\"TextRun SCXW165140185 BCX8\" lang=\"EN-US\" xml:lang=\"EN-US\" data-contrast=\"auto\"><span class=\"NormalTextRun SCXW165140185 BCX8\">Managed identity with a scoped data role<\/span><\/span><span class=\"EOP Selected SCXW165140185 BCX8\" data-ccp-props=\"{}\">\u00a0<\/span><\/td>\n<\/tr>\n<tr>\n<td style=\"width: 14.7977%;\"><span class=\"TextRun SCXW100972453 BCX8\" lang=\"EN-US\" xml:lang=\"EN-US\" data-contrast=\"auto\"><span class=\"NormalTextRun SCXW100972453 BCX8\">Site reliability engineers<\/span><\/span><span class=\"EOP Selected SCXW100972453 BCX8\" data-ccp-props=\"{}\">\u00a0<\/span><\/td>\n<td style=\"width: 22.7792%;\"><span class=\"TextRun SCXW182176367 BCX8\" lang=\"EN-US\" xml:lang=\"EN-US\" data-contrast=\"auto\"><span class=\"NormalTextRun SCXW182176367 BCX8\">Diagnose health and configuration<\/span><\/span><span class=\"EOP Selected SCXW182176367 BCX8\" data-ccp-props=\"{}\">\u00a0<\/span><\/td>\n<td style=\"width: 26.8029%;\"><span class=\"TextRun SCXW128159421 BCX8\" lang=\"EN-US\" xml:lang=\"EN-US\" data-contrast=\"auto\"><span class=\"NormalTextRun SCXW128159421 BCX8\">Cosmos DB Operator; temporary data access if needed<\/span><\/span><span class=\"EOP Selected SCXW128159421 BCX8\" data-ccp-props=\"{}\">\u00a0<\/span><\/td>\n<\/tr>\n<tr>\n<td style=\"width: 14.7977%;\"><span class=\"TextRun SCXW42868309 BCX8\" lang=\"EN-US\" xml:lang=\"EN-US\" data-contrast=\"auto\"><span class=\"NormalTextRun SCXW42868309 BCX8\">Data analysts<\/span><\/span><span class=\"EOP Selected SCXW42868309 BCX8\" data-ccp-props=\"{}\">\u00a0<\/span><\/td>\n<td style=\"width: 22.7792%;\"><span class=\"TextRun SCXW154987341 BCX8\" lang=\"EN-US\" xml:lang=\"EN-US\" data-contrast=\"auto\"><span class=\"NormalTextRun SCXW154987341 BCX8\">Run approved read-only queries<\/span><\/span><span class=\"EOP Selected SCXW154987341 BCX8\" data-ccp-props=\"{}\">\u00a0<\/span><\/td>\n<td style=\"width: 26.8029%;\"><span class=\"TextRun SCXW118530815 BCX8\" lang=\"EN-US\" xml:lang=\"EN-US\" data-contrast=\"auto\"><span class=\"NormalTextRun SCXW118530815 BCX8\">Built-in Data Reader on reporting data<\/span><\/span><span class=\"EOP Selected SCXW118530815 BCX8\" data-ccp-props=\"{}\">\u00a0<\/span><\/td>\n<\/tr>\n<tr>\n<td style=\"width: 14.7977%;\"><span class=\"TextRun SCXW253615586 BCX8\" lang=\"EN-US\" xml:lang=\"EN-US\" data-contrast=\"auto\"><span class=\"NormalTextRun SCXW253615586 BCX8\">Platform engineers<\/span><\/span><span class=\"EOP Selected SCXW253615586 BCX8\" data-ccp-props=\"{}\">\u00a0<\/span><\/td>\n<td style=\"width: 22.7792%;\"><span class=\"TextRun SCXW9650905 BCX8\" lang=\"EN-US\" xml:lang=\"EN-US\" data-contrast=\"auto\"><span class=\"NormalTextRun SCXW9650905 BCX8\">Manage accounts, containers, and throughput<\/span><\/span><span class=\"EOP Selected SCXW9650905 BCX8\" data-ccp-props=\"{}\">\u00a0<\/span><\/td>\n<td style=\"width: 26.8029%;\"><span class=\"TextRun SCXW3029177 BCX8\" lang=\"EN-US\" xml:lang=\"EN-US\" data-contrast=\"auto\"><span class=\"NormalTextRun SCXW3029177 BCX8\">Cosmos DB Operator or a custom Azure role<\/span><\/span><span class=\"EOP Selected SCXW3029177 BCX8\" data-ccp-props=\"{}\">\u00a0<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>The two built-in data roles cover many workloads:<\/p>\n<table style=\"border-collapse: collapse; width: 47.2296%; height: 75px;\">\n<tbody>\n<tr>\n<td style=\"width: 39.4889%;\"><strong>If the identity needs to&#8230;<\/strong><\/td>\n<td style=\"width: 60.5111%;\"><strong>Start with&#8230;<\/strong><\/td>\n<\/tr>\n<tr>\n<td style=\"width: 39.4889%;\"><span class=\"TextRun SCXW133192785 BCX8\" lang=\"EN-US\" xml:lang=\"EN-US\" data-contrast=\"auto\"><span class=\"NormalTextRun SCXW133192785 BCX8\">Read items, run queries, and read the change feed<\/span><\/span><\/td>\n<td style=\"width: 60.5111%;\"><span class=\"TextRun SCXW228306644 BCX8\" lang=\"EN-US\" xml:lang=\"EN-US\" data-contrast=\"auto\"><span class=\"NormalTextRun SCXW228306644 BCX8\">Cosmos DB Built-in Data Reader<\/span><\/span><span class=\"EOP Selected SCXW228306644 BCX8\" data-ccp-props=\"{}\">\u00a0<\/span><\/td>\n<\/tr>\n<tr>\n<td style=\"width: 39.4889%;\"><span class=\"TextRun SCXW28324026 BCX8\" lang=\"EN-US\" xml:lang=\"EN-US\" data-contrast=\"auto\"><span class=\"NormalTextRun SCXW28324026 BCX8\">Read, create, update, and <\/span><span class=\"NormalTextRun SCXW28324026 BCX8\">delete<\/span><span class=\"NormalTextRun SCXW28324026 BCX8\"> items<\/span><\/span><\/td>\n<td style=\"width: 60.5111%;\"><span class=\"TextRun SCXW224959750 BCX8\" lang=\"EN-US\" xml:lang=\"EN-US\" data-contrast=\"auto\"><span class=\"NormalTextRun SCXW224959750 BCX8\">Cosmos DB Built-in Data Contributor<\/span><\/span><span class=\"EOP Selected SCXW224959750 BCX8\" data-ccp-props=\"{}\">\u00a0<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><span data-contrast=\"auto\">Data contributor includes delete permission. If an application should write but never delete, create a custom data role with only the required actions.<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/p>\n<p><span data-contrast=\"auto\">For control-plane work,\u202f<\/span><b><span data-contrast=\"auto\">Cosmos DB operator<\/span><\/b><span data-contrast=\"auto\">\u202fis often safer than a broad contributor role. It can manage Azure Cosmos DB resources but prevents access to account keys and connection strings.<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/p>\n<h3><span class=\"TextRun SCXW210178640 BCX8\" lang=\"EN-US\" xml:lang=\"EN-US\" data-contrast=\"none\"><span class=\"NormalTextRun SCXW210178640 BCX8\" data-ccp-parastyle=\"heading 2\">Use groups for people and managed identities for applications<\/span><\/span><span class=\"EOP Selected SCXW210178640 BCX8\" data-ccp-props=\"{&quot;134245418&quot;:true,&quot;134245529&quot;:true,&quot;335559738&quot;:160,&quot;335559739&quot;:80}\">\u00a0<\/span><\/h3>\n<p><span data-contrast=\"auto\">Direct assignments to individual users become difficult to track as people join, change teams, and leave. Assign roles to Microsoft Entra security groups instead.<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/p>\n<p><span data-contrast=\"auto\">A group name should describe the service, environment, and responsibility:<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/p>\n<p><code><span class=\"LineBreakBlob BlobObject DragDrop SCXW204982456 BCX8\"><span class=\"SCXW204982456 BCX8\">cosmos-orders-dev-contributors <\/span><br class=\"SCXW204982456 BCX8\" \/><\/span><span class=\"LineBreakBlob BlobObject DragDrop SCXW204982456 BCX8\"><span class=\"SCXW204982456 BCX8\">cosmos-orders-prod-data-readers <\/span><br class=\"SCXW204982456 BCX8\" \/><\/span><span class=\"TextRun SCXW204982456 BCX8\" lang=\"EN-US\" xml:lang=\"EN-US\" data-contrast=\"auto\"><span class=\"NormalTextRun SCXW204982456 BCX8\"> cosmos-orders-prod-operators<\/span><\/span><\/code><\/p>\n<p><span data-contrast=\"auto\">When a developer changes teams, you update group membership rather than searching for assignments across subscriptions and accounts.<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/p>\n<p><span data-contrast=\"auto\">Applications should not share those human access groups. Give each workload its own managed identity. An orders API might need Data Contributor on the orders container, while a reporting job needs Data Reader on a reporting database. Separate identities make both permissions and activity easier to understand.<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/p>\n<p><span data-contrast=\"auto\">Deployment automation should also use a different identity from the running application. Creating containers and processing items are different jobs.<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/p>\n<h3><span class=\"TextRun SCXW66799448 BCX8\" lang=\"EN-US\" xml:lang=\"EN-US\" data-contrast=\"none\"><span class=\"NormalTextRun SCXW66799448 BCX8\" data-ccp-parastyle=\"heading 2\">Scope each assignment to the work<\/span><\/span><\/h3>\n<p><span data-contrast=\"auto\">A data-plane role can be assigned at the account, database, or container level. Choose the smallest scope that lets the identity do its job.<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/p>\n<p><span data-contrast=\"auto\">For example, an application that processes orders can use Data Contributor on the orders container instead of the entire account. An analyst can use Data Reader on a reporting database without receiving access to operational data.<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/p>\n<p><span data-contrast=\"auto\">Keep environments separate. Development access should not silently become production access.<\/span><\/p>\n<table style=\"border-collapse: collapse; width: 39.5768%; height: 96px;\">\n<tbody>\n<tr style=\"height: 24px;\">\n<td style=\"width: 16.095%; height: 24px;\"><strong>Environement<\/strong><\/td>\n<td style=\"width: 23.4828%; height: 24px;\"><strong>Useful human-access default<\/strong><\/td>\n<\/tr>\n<tr style=\"height: 24px;\">\n<td style=\"width: 16.095%; height: 24px;\">Development<\/td>\n<td style=\"width: 23.4828%; height: 24px;\">Contributor access within the team&#8217;s resources<\/td>\n<\/tr>\n<tr style=\"height: 24px;\">\n<td style=\"width: 16.095%; height: 24px;\">Test<\/td>\n<td style=\"width: 23.4828%; height: 24px;\">Access required for deployment and testing<\/td>\n<\/tr>\n<tr style=\"height: 24px;\">\n<td style=\"width: 16.095%; height: 24px;\">Production<\/td>\n<td style=\"width: 23.4828%; height: 24px;\">No data access or read-only access, with elevation<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><span class=\"TextRun SCXW127124762 BCX8\" lang=\"EN-US\" xml:lang=\"EN-US\" data-contrast=\"auto\"><span class=\"NormalTextRun SCXW127124762 BCX8\">Scope and role work together. A narrow role <\/span><span class=\"NormalTextRun ContextualSpellingAndGrammarErrorV2Themed SCXW127124762 BCX8\">at<\/span><span class=\"NormalTextRun SCXW127124762 BCX8\"> account scope might still expose more data than necessary. <\/span><span class=\"NormalTextRun SCXW127124762 BCX8\">A broad role at container scope might still allow actions the workload should not perform.<\/span><\/span><span class=\"EOP Selected SCXW127124762 BCX8\" data-ccp-props=\"{}\">\u00a0<\/span><\/p>\n<h3 aria-level=\"2\"><span data-contrast=\"none\">Make production elevation temporary<\/span><span data-ccp-props=\"{&quot;134245418&quot;:true,&quot;134245529&quot;:true,&quot;335559738&quot;:160,&quot;335559739&quot;:80}\">\u00a0<\/span><\/h3>\n<p><span data-contrast=\"auto\">Production incidents sometimes require more access. That does not mean the access must be permanent.<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/p>\n<p><span data-contrast=\"auto\">Use Microsoft Entra Privileged Identity Management for eligible Azure RBAC assignments. For Cosmos DB data-plane access, use a controlled process that adds the responder to a dedicated group, records the reason, and removes the membership after a short period.<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/p>\n<p><span data-contrast=\"auto\">The goal is not to slow down incident response. It is to prevent access granted during an incident from remaining in place.<\/span><\/p>\n<h3 aria-level=\"2\"><span data-contrast=\"none\">Account keys can bypass the model<\/span><span data-ccp-props=\"{&quot;134245418&quot;:true,&quot;134245529&quot;:true,&quot;335559738&quot;:160,&quot;335559739&quot;:80}\">\u00a0<\/span><\/h3>\n<p><span data-contrast=\"auto\">An identity that can retrieve an account key can use that key for broad data access while key-based authentication is enabled. That can undermine carefully scoped data-plane roles.<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/p>\n<p><span data-contrast=\"auto\">Prefer Microsoft Entra authentication for people and managed identities for Azure workloads. Migrate existing applications deliberately:<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/p>\n<ol>\n<li><span data-contrast=\"auto\">Inventory applications, scripts, notebooks, and tools that use keys.<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/li>\n<li aria-setsize=\"-1\" data-leveltext=\"%1.\" data-font=\"\" data-listid=\"1\" data-list-defn-props=\"{&quot;335552541&quot;:0,&quot;335559685&quot;:720,&quot;335559991&quot;:360,&quot;469769242&quot;:[65533,0],&quot;469777803&quot;:&quot;left&quot;,&quot;469777804&quot;:&quot;%1.&quot;,&quot;469777815&quot;:&quot;multilevel&quot;}\" data-aria-posinset=\"2\" data-aria-level=\"1\"><span data-contrast=\"auto\">Give each workload an identity and the required data role.<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/li>\n<li aria-setsize=\"-1\" data-leveltext=\"%1.\" data-font=\"\" data-listid=\"1\" data-list-defn-props=\"{&quot;335552541&quot;:0,&quot;335559685&quot;:720,&quot;335559991&quot;:360,&quot;469769242&quot;:[65533,0],&quot;469777803&quot;:&quot;left&quot;,&quot;469777804&quot;:&quot;%1.&quot;,&quot;469777815&quot;:&quot;multilevel&quot;}\" data-aria-posinset=\"2\" data-aria-level=\"1\"><span data-contrast=\"auto\">Test every required operation and environment.<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/li>\n<li aria-setsize=\"-1\" data-leveltext=\"%1.\" data-font=\"\" data-listid=\"1\" data-list-defn-props=\"{&quot;335552541&quot;:0,&quot;335559685&quot;:720,&quot;335559991&quot;:360,&quot;469769242&quot;:[65533,0],&quot;469777803&quot;:&quot;left&quot;,&quot;469777804&quot;:&quot;%1.&quot;,&quot;469777815&quot;:&quot;multilevel&quot;}\" data-aria-posinset=\"2\" data-aria-level=\"1\"><span data-contrast=\"auto\">Rotate keys to invalidate old copies.<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/li>\n<li aria-setsize=\"-1\" data-leveltext=\"%1.\" data-font=\"\" data-listid=\"1\" data-list-defn-props=\"{&quot;335552541&quot;:0,&quot;335559685&quot;:720,&quot;335559991&quot;:360,&quot;469769242&quot;:[65533,0],&quot;469777803&quot;:&quot;left&quot;,&quot;469777804&quot;:&quot;%1.&quot;,&quot;469777815&quot;:&quot;multilevel&quot;}\" data-aria-posinset=\"2\" data-aria-level=\"1\"><span data-contrast=\"auto\">Disable local authentication after every dependency has migrated.<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/li>\n<\/ol>\n<p><span data-contrast=\"auto\">Do not disable key-based authentication before verifying all working paths. Treat the change as a migration, not a switch you flip without testing.<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><\/p>\n<p>Refer to<a href=\"https:\/\/www.aka.ms\/safe-key-rotation\"> safe key rotation in Azure Cosmos DB<\/a> to get visibility into key usage.<\/p>\n<h3><span class=\"TextRun SCXW61472298 BCX8\" lang=\"EN-US\" xml:lang=\"EN-US\" data-contrast=\"none\"><span class=\"NormalTextRun SCXW61472298 BCX8\" data-ccp-parastyle=\"heading 1\">Wrapping up<\/span><\/span><\/h3>\n<p>A good access model does not need to start with a complex redesign. Start with the access you have today, organize it around the jobs people and applications perform, and keep roles, scope, and duration as narrow as practical.<\/p>\n<p>As your environment grows, let the job drive the access. Give each identity what it needs to do its job, where it needs it, and for no longer than necessary<\/p>\n<h4>What to do next?<\/h4>\n<p>As the team grows, ask four questions for every identity:<\/p>\n<ol>\n<li>What job does it perform?<\/li>\n<li>Is that job on the control plane or the data plane?<\/li>\n<li>What is the narrowest role that supports it?<\/li>\n<li>What is the smallest scope and shortest duration it needs?<\/li>\n<\/ol>\n<p>Those questions scale better than one-off permissions. They give people and applications the access they need without making broad production access the default.<\/p>\n<h2><strong>About Azure Cosmos DB<\/strong><\/h2>\n<p>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.<\/p>\n<p>To stay in the loop on Azure Cosmos DB updates, follow us on\u00a0<a href=\"https:\/\/twitter.com\/AzureCosmosDB\" target=\"_blank\" rel=\"noopener\">X<\/a>,\u00a0<a href=\"https:\/\/aka.ms\/AzureCosmosDBYouTube\" target=\"_blank\" rel=\"noopener\">YouTube<\/a>, and\u00a0<a href=\"https:\/\/www.linkedin.com\/company\/azure-cosmos-db\/\" target=\"_blank\" rel=\"noopener\">LinkedIn<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Your project started with one or two people. Now developers, operators, analysts, and applications all need access to Azure Cosmos DB. Giving everyone the same permissions might feel efficient, but it makes every identity more powerful than its job requires.\u00a0 As your team grows, organize access around jobs, not people. Separate management access from data [&hellip;]<\/p>\n","protected":false},"author":72078,"featured_media":13186,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[14,1918,667],"tags":[],"class_list":["post-13173","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-core-sql-api","category-rbac","category-security"],"acf":[],"blog_post_summary":"<p>Your project started with one or two people. Now developers, operators, analysts, and applications all need access to Azure Cosmos DB. Giving everyone the same permissions might feel efficient, but it makes every identity more powerful than its job requires.\u00a0 As your team grows, organize access around jobs, not people. Separate management access from data [&hellip;]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/cosmosdb\/wp-json\/wp\/v2\/posts\/13173","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/cosmosdb\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/cosmosdb\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cosmosdb\/wp-json\/wp\/v2\/users\/72078"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cosmosdb\/wp-json\/wp\/v2\/comments?post=13173"}],"version-history":[{"count":2,"href":"https:\/\/devblogs.microsoft.com\/cosmosdb\/wp-json\/wp\/v2\/posts\/13173\/revisions"}],"predecessor-version":[{"id":13195,"href":"https:\/\/devblogs.microsoft.com\/cosmosdb\/wp-json\/wp\/v2\/posts\/13173\/revisions\/13195"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cosmosdb\/wp-json\/wp\/v2\/media\/13186"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/cosmosdb\/wp-json\/wp\/v2\/media?parent=13173"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cosmosdb\/wp-json\/wp\/v2\/categories?post=13173"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cosmosdb\/wp-json\/wp\/v2\/tags?post=13173"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}