Hi JeffBobadilla yes I can confirm I used both a Windows Server Core container (for the .NET Framework) sample, and a Windows Server Nano container for the (.NET Core) sample. The article is still valid. I've put my two samples into repos in my GitHub account:
.NET Framework - apwestgarth/DotNetFrameworkSqlDbInWindowsContainer: .NET Framework and Azure SQL DB sample where the authentication method is Managed Identity and the app is deployed in a Windows Container (github.com)
.NET Core - apwestgarth/DotNetCoreSqlDbInWindowsContainer: .NET Core and Azure SQL DB sample where the authentication method is Managed Identity and the app is deployed in a Windows Container (github.com)
I used the article mentioned as the basis to build the application and then I added Docker support and published my app in a container to Azure Container Registry then
- I created a new Resource Group, App Service Plan (P1v3) and Windows Container web app in East US 2, setting the docker container to be the image I had published;
- Once the site was created I enabled Managed Identity via the portal
- I added the Managed Identity to my Azure SQL DB using the steps in the tutorial - Tutorial: Access data with managed identity - Azure App Service | Microsoft Docs
- I browsed the site and confirmed my application was running correctly.
The app itself is currently running at https://apwmsisampleeastus2.azurewebsites.net
Managed Identity is supported across App Service - Windows Code, Windows Containers, Linux Code and Linux Container. We enabled Managed Identities for Windows Containers in App Service in August 2020, so it is possible we may have missed an update to our docs, I am scanning them all to make sure any errors are rectified.
As you are currently still experiencing issues with this functionality, please open a support ticket and we can investigate further and help.