Open hemesh opened 1 month ago
@hemesh Thanks for your feedback! We will investigate and update as appropriate.
@zhenlan, could you please take a look at this issue?
The Quickstart guide is designed to assist you with integrating Azure App Configuration into your .NET Framework applications. It focuses on the setup process and does not specify hosting requirements, as the choice of hosting service is at your discretion. Each hosting service comes with its unique capabilities and constraints.
Azure App Configuration supports authentication via Connection String or Entra ID. Should your chosen hosting service support Managed Identity, it is the preferred method for authentication due to its enhanced security features. If Managed Identity is not available, we recommend securely storing the Connection String in Azure Key Vault and configuring your application to retrieve it at runtime. Set the Connection String in an environment variable when other options are impossible.
Please note that Cloud Services (classic) is a legacy platform and may present more challenges compared to newer services. While Azure App Configuration does not provide a comprehensive list of limitations for all platforms, we encourage users to consult the documentation of their chosen hosting service for specific details.
Something I'd like to see updated please to help others?
I had a long drawn out issue with MS support about using this within an Cloud Service following the guidance and examples on: https://learn.microsoft.com/en-us/azure/azure-app-configuration/overview#why-use-app-configuration. I was eventually pointed out to the following statement to stop me progressing the issue: -
They said because of this, Cloud Service is not supported. The statements are VERY different.
The main issue was the guide here: https://learn.microsoft.com/en-us/azure/azure-app-configuration/quickstart-dotnet-app
For WebRole Cloud Services, we could not set an environment variable to connect to the App Configuration and subsequently any Azure Key Stores via Azure Service Principle connections (as environment variables need setting). For WorkerRole services, this works...
I would recommend that on the first page about examples, it should say that this is not supported on Cloud Service WebRoles.
I did work around it by setting a startup script on deployment that set the environment variable system wide, then forcing via the same script a restart of IIS, then a "start" of IIS (as the restart just stopped it). Either way, I think it needs some guidance, or maybe an FAQ with what I had to do?
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.