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.
Once you've created a .NET template, you should automate the updates of the package using GitHub actions to remove the effort required in publishing updates
Have a site sitting in GitHub that you currently maybe manually deploy to Azure or use some other tool? Why not useGitHub Actionsto quickly and easily publish to Azure. I was pushing a small site (Guid.Empty) to Azure through GitHub and decided to document the couple steps for future me 😋... oh and for you of course 😅
If you don't know yet what GitHub actions are you can read about it on the GitHub Actions feature on GitHub. In short on the 8th of August GitHub announced an update to their actions which you can read about in this blog post. it's a very easy way to automate anything from any event in GitHub.