Logging Module - Errors while deploying locks SecurityInsights

[GregCodeRepos]

What happened? Provide a clear and concise description of the bug, including deployment details.

Deploying logging.bicep failes with SentinelInsights lock enabled in austriaeast.

A lock is created for resSecurityInsightsSolutionLock using api version 2020-05-01 wich is unsupported

{ "code": "DeploymentFailed", "target": "/subscriptions/xxxxxxxxxxx/resourceGroups/rg-xxxxxxxxx/providers/Microsoft.Resources/deployments/-Logging-and-Sentinel-Deployment-20251023075701-03", "message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.", "details": [ { "code": "NoRegisteredProviderFound", "message": "No registered resource provider found for location 'westeurope' and API version '2020-05-01' for type 'workspaces'. The supported api-versions are '2015-03-20, 2015-11-01-preview, 2017-01-01-preview, 2017-03-03-preview, 2017-03-15-preview, 2017-04-26-preview, 2020-03-01-preview, 2020-08-01, 2020-10-01, 2021-03-01-privatepreview, 2021-06-01, 2021-12-01-preview, 2022-10-01, 2023-01-01-preview, 2023-09-01, 2025-02-01, 2025-07-01'. The supported locations are 'eastus, westeurope, southeastasia, australiasoutheast, westcentralus, japaneast, uksouth, centralindia, canadacentral, westus2, australiacentral, australiaeast, francecentral, koreacentral, northeurope, centralus, eastasia, eastus2, southcentralus, northcentralus, westus, ukwest, southafricanorth, brazilsouth, switzerlandnorth, switzerlandwest, germanywestcentral, australiacentral2, uaecentral, uaenorth, japanwest, brazilsoutheast, norwayeast, norwaywest, southindia, koreasouth, jioindiacentral, jioindiawest, qatarcentral, canadaeast, westus3, swedencentral, southafricawest, germanynorth, polandcentral, israelcentral, italynorth, mexicocentral, spaincentral, newzealandnorth, malaysiawest, chilecentral, indonesiacentral'." } ] }

Workaround was used to set global lock to None and manuały create solution lock

Please provide the correlation id associated with your error or bug.

e9fe6a52-0398-4631-b79c-8268a169d0be

What was the expected outcome?

Deployment should complete without issues

Relevant log output

Check previous GitHub issues

• I have searched the issues for this item and found no duplicate

Code of Conduct

• I agree to follow this project's Code of Conduct

[oZakari]

Hi @GregCodeRepos, it looks like there may have been a related RP that wasn't registered. I assume by "manually" creating the resource lock, you created it through the portal? If so, it should have automatically registered the missing RP. Could you try to re-run the Bicep deployment over the top now and see if it completes successfully now?

[GregCodeRepos]

@oZakari - I tried that and result was the same deployment failed, in the end we disabled lock deployment with parameter parSecurityInsightsOnboardingLock.

To clarify SecurityInsightsOnboarding is actually deployed, the issue is related to lock attached to the resource.

[oZakari]

That's interesting, will see if it just an issue with the RP for Security Insights Onboarding that the lock is not able to be associated.