How come you didn't need to set firewall permissions for the production instance? Does Azure Sql Server automatically allow any incoming connections from container instances?
A little late, but you can use managed identities and assign your container app a role in the SQL server in Azure. You assign the identity to the container. Then you use a special connection string that will tell your apo to authorize with Managed identity. You also need to add users and roles in each database for each accessing service. Azure can’t do that for you.
![Serverless with Azure Functions [7 of 8] | .NET on Azure for Beginners](http://i.ytimg.com/vi/29jeJ2N9DGY/mqdefault.jpg)
![Serverless with Azure Functions [7 of 8] | .NET on Azure for Beginners](/img/tr.png)
![Getting Started [1 of 8] | .NET on Azure for Beginners](/img/1.gif)
What a wonderful video series, all MS tutorials should be like this one
why azure managed identity did not worked here, as we already removed the connection string in previous video
Amazing video series learning so much.
Fantastic!! Great content as always!
How do you determine regions best for your app, Ex. in Africa?
How come you didn't need to set firewall permissions for the production instance? Does Azure Sql Server automatically allow any incoming connections from container instances?
A little late, but you can use managed identities and assign your container app a role in the SQL server in Azure.
You assign the identity to the container. Then you use a special connection string that will tell your apo to authorize with Managed identity.
You also need to add users and roles in each database for each accessing service. Azure can’t do that for you.