Forum Discussion
How to update to DesktopVirtualization API v. 2024-04-08-preview or API v. 2024-04-03?
See whether this can help:
1. Check Current API Version: Review your ARM templates, Bicep files, or PowerShell scripts to see if they reference an older API version. For example, in ARM/Bicep, it might look like this:
resource hostPool 'Microsoft.DesktopVirtualization/hostPools@2022-02-10' = {
// Resource properties
}
If you find an older version, update it to 2024-04-03 or 2024-04-08-preview
2. Update Azure CLI: Ensure you have the latest version of Azure CLI installed. You can update it using the following command:
az upgrade
3. Login to Azure: Use az login to authenticate.
4. Modify Scripts: Update the API version in your scripts:
az rest --method get --url "https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DesktopVirtualization/{resourceType}?api-version=2024-04-03"
5. Test in Development Environment: Before deploying the updated API version to production, test it in a development or staging environment to ensure compatibility and functionality.
6. Check Resource Provider: Navigate to the Resource Provider in the Azure portal and check the API version used for your host pools. Ensure it matches the latest version
Hello Kidd_ip and thanks for response
Exactly, my point here is to clarify that unless you use templates, deploy using bicep, terraform, this update will be necessary. In the case that AVD is deployed directly through the Azure portal, it will not be necessary since Microsoft manages it. My question is perhaps because it is a generic email it can create confusion. Correct?
This is my general opinion as well. However, this doesn’t apply to those deploying over the Portal, as we can’t specify the API to use. Azure didn’t provide that information when they sent it.
