Enable Subscription Access for Data Export + Cost Optimization for Cosmos DB

Hello Dinnemidi Ananda Kumar, It sounds like you have three related asks: (1) getting Cosmos DB exports done while the “subscription is disabled”, (2) identifying lower-cost Cosmos DB options for 100+ containers, and (3) planning a migration strategy.

Below is a forum-friendly answer based on the provided docs.

1) “Temporary re-enable subscription” for Cosmos DB export (2–3 hours)

From the provided documentation, the actionable guidance is to open the right kind of Azure support request so you don’t get blocked:

• Ensure you have a paid Azure technical support plan.
• When creating the case, choose Start Again, and select the correct technical service (NOT “Billing” or “Subscription Management”).
• Proceed and request assistance specifically for the technical issue so the case is not closed as a non-qualifying request.

Note: The docs also state that support requests for non-Azure products or Azure technical issues that aren’t handled under the right category may be closed—so the selection matters.

If you can share which Azure portal blade / action is blocked by the “subscription disabled” state (for example, export tooling, Data Explorer, or ARM actions), you’ll help the support engineer target the issue faster.

2) Cosmos DB cost optimization direction (what we can say from the docs)

Cosmos DB costs are driven by:

• Database operations (compute)
• Storage
• Bandwidth/data egress

Compute cost model: Provisioned throughput vs Serverless

Provisioned throughput (RU/s)

• You set RU/s per database/container.
• You’re billed hourly for the maximum provisioned throughput used in that hour.
• You’re charged even if you don’t run workloads because throughput is dedicated to the provisioned resource.

Serverless

• You don’t provision RU/s up front.
• You’re billed based on total Request Units consumed by database operations over the billing period.

So, for cost reduction, the key question is whether your workload is mostly bursty/variable (serverless may help) or mostly steady/predictable (provisioned + right-sizing may help).

How to reduce provisioned-throughput cost (best-practice actions)

Based on the provided “Optimize the costs…” guidance and portal optimization steps:

1. Measure actual RU consumption vs provisioned RU/s

• Look in the Cosmos DB account Metrics for RU usage patterns.

1. Right-size provisioned throughput
   • If containers are consistently underutilized, reduce RU/s to better match demand.
2. Use autoscale when traffic is variable
   • The portal guidance suggests enabling autoscale so RU/s adjusts within a min/max range.
3. Optimize indexing to reduce storage/throughput overhead
   • By default Cosmos DB indexes by default; tuning index policy can reduce storage overhead and avoid unnecessary costs.
4. Optimize storage with TTL / change feed
   • Use TTL to delete data automatically you no longer need.
   • Use change feed for migration to other containers/data stores (no downtime migration concept is mentioned in the docs).

Ways to estimate and forecast costs

• Use the Azure pricing calculator (and log in for your org’s pricing program, if applicable).
• Use Cosmos DB capacity planner / RU estimation guidance (linked from the docs).
• Use Cost Management → Cost analysis for actuals and forecast:
  • Cost analysis supports forecasted cost projection (up to a year) based on recent usage. The docs also provide explicit billing examples showing how provisioned RU/s and serverless RU consumption are charged, which can be used to sanity-check estimates. Reserved capacity / commitment (potential lever)

One of the provided “cost recommendations” mentions:

• Reserved capacity tiers for Cosmos DB can reduce costs if you can commit to RU capacity.

Referance:

• Cosmos DB pricing & billing models: https://azure.microsoft.com/pricing/details/cosmos-db/
• Cosmos DB billing examples / understand your bill: https://learn.microsoft.com/azure/cosmos-db/understand-your-bill#billing-examples
• Plan and manage costs (Cosmos DB): https://learn.microsoft.com/azure/cosmos-db/plan-manage-costs?wt.mc_id=Portal-Microsoft_Azure_Support
• Optimize provisioned throughput cost: https://learn.microsoft.com/azure/cosmos-db/optimize-cost-throughput?wt.mc_id=knowledgesearch_inproduct_azure-cxp-community-insider#data-access-patterns
• Optimize request cost (reads/writes): https://docs.microsoft.com/azure/cosmos-db/optimize-cost-reads-writes
• Optimize storage cost: https://learn.microsoft.com/azure/cosmos-db/optimize-cost-storage?wt.mc_id=knowledgesearch_inproduct_azure-cxp-community-insider#optimize-cost-with-indexing
• Optimize development/testing cost: https://docs.microsoft.com/azure/cosmos-db/optimize-dev-test
• Optimize cost with reserved capacity: https://learn.microsoft.com/azure/cosmos-db/cosmos-db-reserved-capacity
• Optimize multi-region cost: https://docs.microsoft.com/azure/cosmos-db/optimize-cost-regions
• Provisioned throughput vs serverless background (capacity modes): (linked from plan/manage costs page above)
• Download usage details / usage & charges: https://learn.microsoft.com/azure/cost-management-billing/understand/download-azure-daily-usage
• Cost analysis / forecast (Cost Management): https://learn.microsoft.com/azure/cost-management-billing/costs/quick-acm-cost-analysis
• Azure pricing calculator: https://azure.microsoft.com/pricing/calculator/