In the quickstart to install Azure IoT Operations:
If you let the scripts autogenerate the name of the Azure Container Registry instance, then you're likely to get a global name clash in Azure, as they try to try to create an ACR called iotopsclusteracr which already exists.
As a workaround, make sure to add your own ACR instance name in the config file using the key: container_registry.
In the quickstart to install Azure IoT Operations:
If you let the scripts autogenerate the name of the Azure Container Registry instance, then you're likely to get a global name clash in Azure, as they try to try to create an ACR called iotopsclusteracr which already exists.
As a workaround, make sure to add your own ACR instance name in the config file using the key:
container_registry.