Azure Bicep & Microsoft.DevTestLab/schedules cannot get targetResourceId

[Jetelaczek]

Hi all,

I am trying to implement simple thing using Bicep, but somehow cannot get through and I am pretty sure it'll be something stupid.

Using copy loop while creating shutdown schedule, to create a schedule for VMs mentioned in parameter file, but getting 'Code:InvalidScheduleId'. I guess the issue is somewhere around target specification (targetResourceId), but not sure what could be wrong there. Any ideas?

targetResourceId: '/subscriptions/${subscription().subscriptionId}/resourceGroups/${resourceGroup().name}/providers/Microsoft.Compute/virtualMachines/${item.ServerName}-${item.ServerSite}'

Bicep & template:

Error:

######################################################
Bicep:
######################################################

param Par_Location string = resourceGroup().location
param Par_Servers array

resource ShutdownVMs 'Microsoft.DevTestLab/schedules@2018-09-15' = [for item in Par_Servers: {
name: '${item.ServerName}-${item.ServerSite}-ShutdownSchedule'
location: Par_Location
properties: {
status: 'Enabled'
taskType: 'ComputeVmShutdownTask'
dailyRecurrence: {
time: '16:00'
}
timeZoneId: 'Central Europe Standard Time'
targetResourceId: '/subscriptions/${subscription().subscriptionId}/resourceGroups/${resourceGroup().name}/providers/Microsoft.Compute/virtualMachines/${item.ServerName}-${item.ServerSite}'
notificationSettings: {
status: 'Disabled'
notificationLocale: 'en'
timeInMinutes: 30
}
}
}]

######################################################
ERROR:
######################################################

Deploying Azure Resource into: RG-Showcase
Template File in use: .\Templates\Shutdown.bicep
Parameter file in use: .\Parameters\Shutdown.json
VERBOSE: Using Bicep v0.4.1008
VERBOSE: Performing the operation "Creating Deployment" on target "RG-Showcase".
VERBOSE: 9:39:12 - Template is valid.
VERBOSE: 9:39:13 - Create template deployment 'DeployShutdownSchedule'
VERBOSE: 9:39:13 - Checking deployment status in 5 seconds
New-AzResourceGroupDeployment: C:\Users...\Scripts\Shutdown.ps1:13
Line |
13 | New-AzResourceGroupDeployment -Verbose -Name "DeployShutdownSchedule" …
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| 9:39:18 - The deployment 'DeployShutdownSchedule' failed with error(s). Showing 2 out of 2 error(s). Status Message: The schedule should be created in subscription ***, resource group
| RG-Showcase and with name shutdown-computevm-CS01-AMS. (Code:InvalidScheduleId) Status Message: The schedule should be created in subscription ***, resource group RG-Showcase and with
| name shutdown-computevm-CS01-PRG. (Code:InvalidScheduleId) CorrelationId: 65d5eb9e-5922-4fb3-8fa5-758d9bc88d33

DeploymentName : DeployShutdownSchedule
ResourceGroupName : RG-Showcase
ProvisioningState : Failed
Timestamp : 05.11.2021 8:39:14
Mode : Incremental
TemplateLink :
Parameters :
Name Type Value
=============== ========================= ==========
par_Location String westeurope
par_Servers Array [
{
"serverName": "CS01",
"serverRole": "CS",
"roRw": "RW",
"serverSite": "PRG",
"vmSize": "Standard_DS2_v2",
"storageAccountType": "Premium_LRS",
"dataDiskSize": "80",
"windowsFeatures": [
"CS"
]
},
{
"serverName": "CS01",
"serverRole": "CS",
"roRw": "RW",
"serverSite": "AMS",
"vmSize": "Standard_DS2_v2",
"storageAccountType": "Premium_LRS",
"dataDiskSize": "80",
"windowsFeatures": [
"CS"
]
}
]

Outputs :
DeploymentDebugLogLevel :

[brwilkinson]

Hi @Jetelaczek

In this case there is a very specific naming standard required, which is: shutdown-computevm-${computerName}

So just replace whatever you used to name your virtualMachine with computerName above.

Sample here:
https://github.com/brwilkinson/AzureDeploymentFramework/blob/f79d488fb6fd6191629f65d46b98297979464200/ADF/bicep/VM.bicep#L326

In the case of the sample:

// name of vm
name: '${Deployment}-vm${vm.Name}'

// name of schedule
name: 'shutdown-computevm-${Deployment}-vm${vm.Name}'

so computername is: ${Deployment}-vm${vm.Name}

[Jetelaczek]

Hi Ben,

Thanks for your time and help, you're right.

Such stupid thing :)

Enjoy your weekend!

Tomas

[brwilkinson]

Great, yes no problem. The documentation is not great on this in the api specs.