A perfectly stable GitHub Actions deployment to Azure SQL suddenly fails with a misleading 'Identity not found' error. Follow the debugging journey to uncover the real culprit that has nothing to do with the identity.
There is documentation available for Move resources to new resource group or subscription but things are easier to do with exact sample code so here it goes . The steps below will work for moving between Resource Groups as well, you'll just skip some steps that would be obvious.
In the new Azure Portal you create all your resources in Resource Groups, there is also as part of the Azure SDK's a module called AzureResourceManager by default the module loaded for the Azure SDK is AzureServiceManagement. A blurb from one of the Azure documentation page reads
So yesterday I posted Pushing a new project to Chocolatey and I said I would create another post showing how to configure how the Chocolatey install runs and this is that post .