Skip to content

How would you configure your Bicep code for the creation of a storage with advanced threat protection? #1504

Answered by alex-frankel
rpothin asked this question in Q&A
Discussion options

You must be logged in to vote

Have you tried using the bicep decompile command? You can also use the decompile capability in the bicep playground:

Here's the code it generated:

param storageAccountName string {
  metadata: {
    description: 'The name must be unique across all existing storage account names in Azure. It must be 3 to 24 characters long, and can contain only lowercase letters and numbers.'
  }
  default: 'atpstorage${uniqueString(resourceGroup().id)}'
}
param location string {
  metadata: {
    description: 'Storage account location, default is same as resource group location.'
  }
  default: resourceGroup().location
}
param storageAccountKind string {
  allowed: [
    'StorageV2'
    'Storage'
  ]
  me…

Replies: 1 comment 3 replies

Comment options

You must be logged in to vote
3 replies
@rpothin
Comment options

@alex-frankel
Comment options

@rpothin
Comment options

Answer selected by rpothin
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants