Category: Azure

A recent change in the SqlServer PowerShell module has given me a headache this week. I’m running the module with Azure DevOps in a pipeline that is triggering an Azure deployment script within a network-integrated container instance.

System.IO.FileNotFoundException: Could not load file or assembly

The problem this error.

Recently I saw intermittent failures of a Python script. However, in my Azure DevOps pipeline, I don’t really knowingly use Python. After today, it just kept consistently failing, which led me to research this issue with the Azure CLI.

/opt/az/lib/python3.12/site-packages/azure/multiapi/storagev2/fileshare/__init__.py:1: UserWarning: 
pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html. 
The pkg_resources package is slated for removal as early as 2025-11-30. 
Refrain from using this package or pin to Setuptools<81.

I ran into this issue, and after not too long searching, I could already find an open case on GitHub. The root cause of the issue seems to be the latest Azure CLI 2.74.0, which is no longer working as intended.

I started seeing a new issue on June 10th, 2025 that my Azure App Service staging slot was created with the name “staging”, but it became “stagingd5a1” in the domain name.

So four seemingly random characters were added to my azure app service deployment slot name. This became a problem as my pipeline is running health checks on the deployment. These checks, however, are not run on the assigned name but on the expected name which suddenly was no longer correct. It would be possible to obtain the name and use it, but there are also other issues that can emerge from it. The website might not know what portal to return on a random hostname, CORS errors could occur on an unexpected domain.

Microsoft is generally pushing for more secure, randomly generated hostnames.

However, this is not the feature I ran into in this case.

In the Azure DevOps world, moving from one tenant to another is not a very familiar concept based on Microsoft documentation. I had to do exactly this. The Azure DevOps Migration Tools did the trick for most of the ADO Boards-related things.

Repos were copied over by pushing to a new Git source.

Pipelines are stored in the Git repository as YAML and were imported / linked again.

One large task was migrating the pipeline library. You can’t export the values secrets in the library, but I used a tool to make sure to copy everything over. Having the secret variables copied over with empty values was already very valuable to me.

You might have the problem that when you are opening dev.azure.com you will be redirected to portal.azure.com. Likely you were not looking for portal.azure.com but rather for Azure DevOps. This is how you can find your Azure DevOps organization and gain access back.

I’m experiencing issues again with deploying App Services to Azure’s data center in West Europe. In December 2023, I saw a similar issue with DSv5 availability. As of August 9, 2024, I’m stuck with what appears to be capacity issues again. However, it turns out that was not the case.

{
    "code": "DeploymentFailed",
    "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": "Unauthorized",
            "message": "Operation cannot be completed without additional AZ quota. Please file a support ticket to request a limit increase. \r\nAdditional details - Location: West Europe \r\nCurrent Limit (Premium0V3 VMs): 0. \r\nCurrent Usage: 0. \r\nAmount required for this deployment (Premium0V3 VMs): 1. \r\n(Minimum) New Limit that you should request to enable this deployment: 1. \r\nNote that if you experience multiple scaling operations failing (in addition to this one) and need to accommodate the aggregate quota requirements of these operations, you will need to request a higher quota limit than the one currently displayed."
        }
    ]
}

Already published in February 2020 with the “preview”-state, the new Kudu was published on Microsoft’s website. But until recently, I was also not aware that this existed. Now in July 2024, the default link from the Azure portal still leads to the old Kudu, with the new Kudu only available if you know it’s there.