Skip to content

fix: remove enableAnalyticalStorage o…#7074

Draft
Shreyas-Microsoft wants to merge 1 commit into
Azure:mainfrom
Prajwal-Microsoft:psl-modernize-cosmos-analytical-storage-v2
Draft

fix: remove enableAnalyticalStorage o…#7074
Shreyas-Microsoft wants to merge 1 commit into
Azure:mainfrom
Prajwal-Microsoft:psl-modernize-cosmos-analytical-storage-v2

Conversation

@Shreyas-Microsoft

Copy link
Copy Markdown
Contributor

Description

Azure no longer supports enabling Analytical Storage during Cosmos DB account creation, which caused deployments to fail with:

BadRequest: Enabling Analytical Storage during account creation is no longer supported.

The flag was set to true in modules/cosmosDb.bicep but no container in this pattern configures analyticalStorageTtl, so the feature was unused. Removing the explicit value lets the AVM document-db/database-account module default (false) apply, unblocking deployments.

Mirrors microsoft/Modernize-your-code-solution-accelerator#432.

Regenerated main.json from the updated Bicep.

Description

Pipeline Reference

Pipeline
avm.ptn.sa.modernize-your-code

Type of Change

  • Azure Verified Module updates:
    • Bugfix containing backwards-compatible bug fixes, and I have NOT bumped the MAJOR or MINOR version in version.json:
    • Feature update backwards compatible feature updates, and I have bumped the MINOR version in version.json.
    • Breaking changes and I have bumped the MAJOR version in version.json.
    • Update to documentation
  • Update to CI Environment or utilities (Non-module affecting changes)

Checklist

  • I'm sure there are no other open Pull Requests for the same update/change
  • I have run Set-AVMModule locally to generate the supporting module files.
  • My corresponding pipelines / checks run clean and green without any errors or warnings
  • I have updated the module's CHANGELOG.md file with an entry for the next version

…n Cosmos DB account creation

Azure no longer supports enabling Analytical Storage during Cosmos DB account creation, which caused deployments to fail with:

  BadRequest: Enabling Analytical Storage during account creation is no longer supported.

The flag was set to true in modules/cosmosDb.bicep but no container in this pattern configures analyticalStorageTtl, so the feature was unused. Removing the explicit value lets the AVM document-db/database-account module default (false) apply, unblocking deployments.

Mirrors microsoft/Modernize-your-code-solution-accelerator#432.

Regenerated main.json from the updated Bicep.
@microsoft-github-policy-service microsoft-github-policy-service Bot added the Needs: Triage 🔍 Maintainers need to triage still label May 19, 2026
@microsoft-github-policy-service

Copy link
Copy Markdown

Important

The "Needs: Triage 🔍" label must be removed once the triage process is complete!

Tip

For additional guidance on how to triage this issue/PR, see the BRM Issue Triage documentation.

@microsoft-github-policy-service microsoft-github-policy-service Bot added the Type: AVM 🅰️ ✌️ Ⓜ️ This is an AVM related issue label May 19, 2026
@microsoft-github-policy-service

Copy link
Copy Markdown

Important

If this is a module-related PR, being submitted by the sole owner of the module, the AVM core team must review and approve it (as module owners can't approve their own PRs).

To indicate this PR needs the core team''s attention, apply the "Needs: Core Team 🧞" label!

The core team will only review and approve PRs that have this label applied!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Needs: Triage 🔍 Maintainers need to triage still Type: AVM 🅰️ ✌️ Ⓜ️ This is an AVM related issue

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant