Skip to content

bcp135.md

Latest commit

 

History

History
60 lines (42 loc) · 1.51 KB

bcp135.md

File metadata and controls

60 lines (42 loc) · 1.51 KB
title BCP135
description Scope <scope-name> isn't valid for this resource type. Permitted scopes <scope-name>.
ms.topic reference
ms.custom devx-track-bicep
ms.date 10/30/2025

Bicep diagnostic code - BCP135

In Bicep, scopes determine the hierarchical level at which resources are deployed within Azure. ARM provides four deployment scopes—resource group, management group, subscription, and tenant. Resources must be deployed within the allowed scopes. For more information, see Deployment scope.

Description

Scope <scope-name> isn't valid for this resource type. Permitted scopes: <scope-name>.

Level

Error

Solutions

Deploy resources to the permitted scopes.

Examples

The following example raises the diagnostic because storageAccounts can't be deployed at the management group scope.

targetScope = 'managementGroup'

resource storageAccount 'Microsoft.Storage/storageAccounts@2023-05-01' = {
  name: 'demostorage0220'
  location: 'eastus'
  sku: {
    name:  'Standard_LRS'
  }
  kind:  'StorageV2'
}

You can fix the diagnostic by setting the targetScope to resourceGroup.

targetScope = 'resourceGroup'

resource storageAccount 'Microsoft.Storage/storageAccounts@2023-05-01' = {
  name: 'demostorage0220'
  location: 'eastus'
  sku: {
    name:  'Standard_LRS'
  }
  kind:  'StorageV2'
}

Next steps

For more information about Bicep diagnostics, see Bicep core diagnostics.