Deploying APIM Workspace via Bicep script

Hi Laurens van de Venn,

Thank you for posting your question in the Microsoft Q&A forum

Understand from the description that you are encountering an issue with your Bicep script while trying to deploy an API Management (APIM) workspace. The error message you've shared indicates a problem with how the resource naming is structured in relation to nested resources.

Steps:

Name field in the apimWorkspace resource definition to match the expected format. Specifically, you need to separate the apimServiceName and workspaceName properly as part of a full resource ID.

Here’s how you can adjust your Bicep script:

param apimServiceName string
param workspaceName string
param location string
param workspaceDescription string
param resourceGroupName string // Add a parameter for the resource group name

// Create APIM Workspace
resource apimWorkspace 'Microsoft.ApiManagement/service/workspaces@2023-03-01-preview' = {
  name: '${apimServiceName}/workspaces/${workspaceName}' // Correcting the name format
  location: location
  properties: {
    description: workspaceDescription
  }
}

Key Changes:

1. Resource Name Format: The name is adjusted to apimServiceName/workspaces/workspaceName, which is the correct structure for nested resources in APIM.
2. Resource Group: Ensure you're deploying the APIM service and workspace to the correct resource group.

• Azure Resource Manager - Resource Name Rules
• Deploy Application Insights Resources with Bicep
• Bicep Resource Declaration
• Troubleshooting template deployment errors

If you have any further questions, feel free to reach out.

Kindly let us know if the above helps or you need further assistance on this issue.

Please "Upvote" if the information helped you. This will help us and others in the community as well.

Thanks