Observed Signal · Jul 20, 2026 · Technical Guide · Source: DEV Community · Impact: 2/5 · Sentiment: Neutral
How to Change Partition Key in Azure Cosmos DB
The article explains that a container's partition key in Azure Cosmos DB is fixed at creation and cannot be changed in-place, so changing keys requires moving data to a new container. It outlines four approaches and their tradeoffs: the Azure portal "Change partition key" feature (managed, low effort), container copy jobs via CLI (scriptable, online/offline modes), a custom migration pipeline using bulk ingestion/ADF/Spark and change feed (maximum control), and a Global Secondary Index (GSI) to support different read patterns without moving writes. Key operational considerations include online vs offline copy modes, RU cost impacts, prerequisites like continuous backup and all-versions-and-deletes change feed, TTL behavior, and creation-time-only settings like hierarchical partition keys.
Practical technical guidance for Cosmos DB partition-key changes affects cloud data architecture and migration planning but is not a platform policy or major product announcement.
Track Microsoft Signals & Market Shifts in Real-Time
Polaris7 autonomous intelligence agents track regulatory filings, primary sources, executive changes, and deal flow 24/7. Create your free Explorer workspace to monitor these entities.
Key Takeaways & Evidence Grounding
- A container's partition key in Azure Cosmos DB is fixed at creation and cannot be changed in place.
- Changing the partition key requires moving data into a new container; options are: portal Change partition key feature, container copy jobs, or a custom migration.
- Container copy jobs (the engine behind the portal feature) support online and offline modes; online mode allows writes during copy but doubles RU charges for source writes and requires continuous backup plus all-versions-and-deletes change feed.
- Global Secondary Index (GSI) creates a separate, read-only, auto-synced container with a different partition key to fix read patterns without moving writes.
- Some settings (e.g., hierarchical partition keys) can only be set at container creation, so the destination container is the opportunity to enable them.
Connected Companies & Entities
1 Entity mapped“Need a different partition key in Azure Cosmos DB? Pick the right approach...”
Ontology Mapping & Concepts
Related Market Signals & Shifts
Recent verified developments and strategic activity across this market segment.
When SQL Isn't Right: Cosmos DB vs Blob Storage
This technical blog post explains when relational SQL databases are the wrong fit and outlines two Azure alternatives: Azure Cosmos DB for flexible JSON documents and Azure Blob Storage for unstructured files. It describes Cosmos DB concepts (account, database, container, item), emphasizes the critical importance of choosing an appropriate partition key, and explains billing via Request Units with provisioned and serverless modes. For Blob Storage the article covers blob types (block, append, page), storage tiers (Hot, Cool, Archive), and Shared Access Signatures (SAS) for scoped temporary access. The author contrasts Azure SQL, Cosmos DB and Blob Storage and offers practical guidance for matching data shape and access patterns to the right Azure service.
DynamoDB Hot Partition: Leaderboard Scaling Explained
A DEV Community post (Jul 21, 2026) presents a DynamoDB scaling scenario: a gaming platform stores leaderboards using game_id as the partition key; one title, “battle-royale,” generates 78% of reads and causes throttling and high P99 latency despite table-level consumed RCUs appearing well below provisioned capacity. The correct diagnosis is a hot partition: DynamoDB enforces per-partition throughput ceilings (3,000 RCUs / 1,000 WCUs), so adding table-level RCUs does not relieve a single overloaded partition. The post explains why a missing GSI is not the cause and recommends two mitigations: migrate to DynamoDB on‑demand capacity mode (more adaptive per-partition scaling) or shard the partition key (add random suffixes and use scatter‑gather reads).
Microsoft Xbox creates new division for films, series, parks
Microsoft's Xbox gaming division announced the creation of a new business unit dedicated to films, television series, and theme park attractions. The move signals an expansion into entertainment and immersive experiences beyond video games, leveraging Xbox's intellectual property. This strategic diversification is part of Microsoft's broader ambition to grow its media and entertainment footprint, following trends seen across the industry. The new division will focus on developing and producing content based on Xbox franchises, potentially opening new revenue streams for the company. Financial details or a timeline for the division's operations have not been disclosed.
Track Real-Time Market Signals & Shifts
Set up custom watchlists to receive automated, evidence-grounded executive digests whenever material signals or shifts occur across your tracked landscape.