What does the connectionString attribute look like in AzureKeyVault ConfigurationBuilder?











up vote
0
down vote

favorite












I'm trying to use the new AzureKeyVault ConfigurationBuilder in a .NET 4.7.1 MVC app and keep getting configuration errors when I run it locally:



Configuration Error
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: An error occurred loading a configuration file: One or more errors occurred.

Source Error:


Line 13: </builders>
Line 14: </configBuilders>
Line 15: <appSettings configBuilders="AzureKeyVault">
Line 16: <add key="webpages:Version" value="3.0.0.0" />
Line 17: <add key="webpages:Enabled" value="false" />


After creating a new .NET Framework 4.7.1 ASP.NET MVC web project, I added a connected service to Azure Key Vault and targeted an existing vault. My web.config then looked included this section:



<configuration>
<configSections>
<section name="configBuilders" type="System.Configuration.ConfigurationBuildersSection, System.Configuration, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" restartOnExternalChanges="false" requirePermission="false" />
</configSections>
<configBuilders>
<builders>
<add name="AzureKeyVault" vaultName="my-test-keyvault" connectionString="" type="Microsoft.Configuration.ConfigurationBuilders.AzureKeyVaultConfigBuilder, Microsoft.Configuration.ConfigurationBuilders.Azure, Version=1.0.0.0, Culture=neutral" vaultUri="https://WebApplication1-12-kv.vault.azure.net" />
</builders>
</configBuilders>
<appSettings configBuilders="AzureKeyVault">
<add key="webpages:Version" value="3.0.0.0" />
<add key="webpages:Enabled" value="false" />
<add key="ClientValidationEnabled" value="true" />
<add key="UnobtrusiveJavaScriptEnabled" value="true" />
</appSettings>
<system.web>
<compilation debug="true" targetFramework="4.7.1" />
<httpRuntime targetFramework="4.7.1" />


I've been scouring the internet trying to find examples of what the connectionString should look like but I haven't had any success. The documentation states:




The vaultName is required. The other attributes allow you some manual control about which vault to connect to, but are only necessary if the application is not running in an environment that works magically with Microsoft.Azure.Services.AppAuthentication. The Azure Services Authentication library is used to automatically pick up connection information from the execution environment if possible, but you can override that feature by providing a connection string instead.




Any recommendations or pointers here? Thanks.










share|improve this question


























    up vote
    0
    down vote

    favorite












    I'm trying to use the new AzureKeyVault ConfigurationBuilder in a .NET 4.7.1 MVC app and keep getting configuration errors when I run it locally:



    Configuration Error
    Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

    Parser Error Message: An error occurred loading a configuration file: One or more errors occurred.

    Source Error:


    Line 13: </builders>
    Line 14: </configBuilders>
    Line 15: <appSettings configBuilders="AzureKeyVault">
    Line 16: <add key="webpages:Version" value="3.0.0.0" />
    Line 17: <add key="webpages:Enabled" value="false" />


    After creating a new .NET Framework 4.7.1 ASP.NET MVC web project, I added a connected service to Azure Key Vault and targeted an existing vault. My web.config then looked included this section:



    <configuration>
    <configSections>
    <section name="configBuilders" type="System.Configuration.ConfigurationBuildersSection, System.Configuration, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" restartOnExternalChanges="false" requirePermission="false" />
    </configSections>
    <configBuilders>
    <builders>
    <add name="AzureKeyVault" vaultName="my-test-keyvault" connectionString="" type="Microsoft.Configuration.ConfigurationBuilders.AzureKeyVaultConfigBuilder, Microsoft.Configuration.ConfigurationBuilders.Azure, Version=1.0.0.0, Culture=neutral" vaultUri="https://WebApplication1-12-kv.vault.azure.net" />
    </builders>
    </configBuilders>
    <appSettings configBuilders="AzureKeyVault">
    <add key="webpages:Version" value="3.0.0.0" />
    <add key="webpages:Enabled" value="false" />
    <add key="ClientValidationEnabled" value="true" />
    <add key="UnobtrusiveJavaScriptEnabled" value="true" />
    </appSettings>
    <system.web>
    <compilation debug="true" targetFramework="4.7.1" />
    <httpRuntime targetFramework="4.7.1" />


    I've been scouring the internet trying to find examples of what the connectionString should look like but I haven't had any success. The documentation states:




    The vaultName is required. The other attributes allow you some manual control about which vault to connect to, but are only necessary if the application is not running in an environment that works magically with Microsoft.Azure.Services.AppAuthentication. The Azure Services Authentication library is used to automatically pick up connection information from the execution environment if possible, but you can override that feature by providing a connection string instead.




    Any recommendations or pointers here? Thanks.










    share|improve this question
























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      I'm trying to use the new AzureKeyVault ConfigurationBuilder in a .NET 4.7.1 MVC app and keep getting configuration errors when I run it locally:



      Configuration Error
      Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

      Parser Error Message: An error occurred loading a configuration file: One or more errors occurred.

      Source Error:


      Line 13: </builders>
      Line 14: </configBuilders>
      Line 15: <appSettings configBuilders="AzureKeyVault">
      Line 16: <add key="webpages:Version" value="3.0.0.0" />
      Line 17: <add key="webpages:Enabled" value="false" />


      After creating a new .NET Framework 4.7.1 ASP.NET MVC web project, I added a connected service to Azure Key Vault and targeted an existing vault. My web.config then looked included this section:



      <configuration>
      <configSections>
      <section name="configBuilders" type="System.Configuration.ConfigurationBuildersSection, System.Configuration, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" restartOnExternalChanges="false" requirePermission="false" />
      </configSections>
      <configBuilders>
      <builders>
      <add name="AzureKeyVault" vaultName="my-test-keyvault" connectionString="" type="Microsoft.Configuration.ConfigurationBuilders.AzureKeyVaultConfigBuilder, Microsoft.Configuration.ConfigurationBuilders.Azure, Version=1.0.0.0, Culture=neutral" vaultUri="https://WebApplication1-12-kv.vault.azure.net" />
      </builders>
      </configBuilders>
      <appSettings configBuilders="AzureKeyVault">
      <add key="webpages:Version" value="3.0.0.0" />
      <add key="webpages:Enabled" value="false" />
      <add key="ClientValidationEnabled" value="true" />
      <add key="UnobtrusiveJavaScriptEnabled" value="true" />
      </appSettings>
      <system.web>
      <compilation debug="true" targetFramework="4.7.1" />
      <httpRuntime targetFramework="4.7.1" />


      I've been scouring the internet trying to find examples of what the connectionString should look like but I haven't had any success. The documentation states:




      The vaultName is required. The other attributes allow you some manual control about which vault to connect to, but are only necessary if the application is not running in an environment that works magically with Microsoft.Azure.Services.AppAuthentication. The Azure Services Authentication library is used to automatically pick up connection information from the execution environment if possible, but you can override that feature by providing a connection string instead.




      Any recommendations or pointers here? Thanks.










      share|improve this question













      I'm trying to use the new AzureKeyVault ConfigurationBuilder in a .NET 4.7.1 MVC app and keep getting configuration errors when I run it locally:



      Configuration Error
      Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

      Parser Error Message: An error occurred loading a configuration file: One or more errors occurred.

      Source Error:


      Line 13: </builders>
      Line 14: </configBuilders>
      Line 15: <appSettings configBuilders="AzureKeyVault">
      Line 16: <add key="webpages:Version" value="3.0.0.0" />
      Line 17: <add key="webpages:Enabled" value="false" />


      After creating a new .NET Framework 4.7.1 ASP.NET MVC web project, I added a connected service to Azure Key Vault and targeted an existing vault. My web.config then looked included this section:



      <configuration>
      <configSections>
      <section name="configBuilders" type="System.Configuration.ConfigurationBuildersSection, System.Configuration, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" restartOnExternalChanges="false" requirePermission="false" />
      </configSections>
      <configBuilders>
      <builders>
      <add name="AzureKeyVault" vaultName="my-test-keyvault" connectionString="" type="Microsoft.Configuration.ConfigurationBuilders.AzureKeyVaultConfigBuilder, Microsoft.Configuration.ConfigurationBuilders.Azure, Version=1.0.0.0, Culture=neutral" vaultUri="https://WebApplication1-12-kv.vault.azure.net" />
      </builders>
      </configBuilders>
      <appSettings configBuilders="AzureKeyVault">
      <add key="webpages:Version" value="3.0.0.0" />
      <add key="webpages:Enabled" value="false" />
      <add key="ClientValidationEnabled" value="true" />
      <add key="UnobtrusiveJavaScriptEnabled" value="true" />
      </appSettings>
      <system.web>
      <compilation debug="true" targetFramework="4.7.1" />
      <httpRuntime targetFramework="4.7.1" />


      I've been scouring the internet trying to find examples of what the connectionString should look like but I haven't had any success. The documentation states:




      The vaultName is required. The other attributes allow you some manual control about which vault to connect to, but are only necessary if the application is not running in an environment that works magically with Microsoft.Azure.Services.AppAuthentication. The Azure Services Authentication library is used to automatically pick up connection information from the execution environment if possible, but you can override that feature by providing a connection string instead.




      Any recommendations or pointers here? Thanks.







      asp.net-mvc visual-studio-2017 .net-framework-version azure-keyvault






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 19 at 22:23









      beaudetious

      1,38532454




      1,38532454
























          2 Answers
          2






          active

          oldest

          votes

















          up vote
          1
          down vote



          accepted










          The documentation linked in the linked article (Announcing .NET 4.7.1 Tools for the Cloud) is out of date. There is no clientId and clientSecret properties on the AzureKeyVaultConfigBuilder class.



          There is a connectionString property however. Details on how to build that connection string when running locally are in this article: Service-to-service authentication to Azure Key Vault using .NET.



          This is the method that worked for me:



          RunAs=App;AppId={AppId};TenantId={TenantId};AppKey={ClientSecret}


          All three of these values (AppId, TenantId and AppKey) are available in the application's AD entry in Azure.






          share|improve this answer





















          • Glad to see you have solved problem, it seems that mine is not well considered.
            – Joey Cai
            Nov 22 at 2:22




















          up vote
          0
          down vote













          I could reproduce your problem in local with the following code:



          <add name="AzureKeyVault"
          mode="Strict"
          vaultName="MyVaultName"
          type="Microsoft.Configuration.ConfigurationBuilders.AzureKeyVaultConfigBuilder, Microsoft.Configuration.ConfigurationBuilders.Azure" />


          If your application is running on an Azure service that has , this is all you need to read configuration from the vault and add it to your application. Conversely, if you are not running on a service with MSI, you can still use the vault by adding the following attributes:



          clientId – the Azure Active Directory application key that has access to your key vault.



          clientSecret – the Azure Active Directory application secret that corresponds to the clientId



          I test with following code and it works well, you could refer to it.



          <configSections>
          <section name="configBuilders" type="System.Configuration.ConfigurationBuildersSection, System.Configuration, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" restartOnExternalChanges="false" requirePermission="false" />
          </configSections>
          <configBuilders>
          <builders>
          <add name="KeyVault" mode="Strict" prefix="conn_" stripPrefix="true"
          clientId="MyId" clientSecret="mySecret" vaultName="MyVault"
          type="Microsoft.Configuration.ConfigurationBuilders.AzureKeyVaultConfigBuilder, Microsoft.Configuration.ConfigurationBuilders.Azure" />
          </builders>
          </configBuilders>


          For more details, you could refer to this article.






          share|improve this answer





















          • I have read that article as well and looking at the source code, there is no clientId or clientSecret properties for AzureKeyVaultConfigBuilder: github.com/aspnet/MicrosoftConfigurationBuilders/blob/master/…
            – beaudetious
            Nov 20 at 11:06











          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53383511%2fwhat-does-the-connectionstring-attribute-look-like-in-azurekeyvault-configuratio%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          2 Answers
          2






          active

          oldest

          votes








          2 Answers
          2






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          up vote
          1
          down vote



          accepted










          The documentation linked in the linked article (Announcing .NET 4.7.1 Tools for the Cloud) is out of date. There is no clientId and clientSecret properties on the AzureKeyVaultConfigBuilder class.



          There is a connectionString property however. Details on how to build that connection string when running locally are in this article: Service-to-service authentication to Azure Key Vault using .NET.



          This is the method that worked for me:



          RunAs=App;AppId={AppId};TenantId={TenantId};AppKey={ClientSecret}


          All three of these values (AppId, TenantId and AppKey) are available in the application's AD entry in Azure.






          share|improve this answer





















          • Glad to see you have solved problem, it seems that mine is not well considered.
            – Joey Cai
            Nov 22 at 2:22

















          up vote
          1
          down vote



          accepted










          The documentation linked in the linked article (Announcing .NET 4.7.1 Tools for the Cloud) is out of date. There is no clientId and clientSecret properties on the AzureKeyVaultConfigBuilder class.



          There is a connectionString property however. Details on how to build that connection string when running locally are in this article: Service-to-service authentication to Azure Key Vault using .NET.



          This is the method that worked for me:



          RunAs=App;AppId={AppId};TenantId={TenantId};AppKey={ClientSecret}


          All three of these values (AppId, TenantId and AppKey) are available in the application's AD entry in Azure.






          share|improve this answer





















          • Glad to see you have solved problem, it seems that mine is not well considered.
            – Joey Cai
            Nov 22 at 2:22















          up vote
          1
          down vote



          accepted







          up vote
          1
          down vote



          accepted






          The documentation linked in the linked article (Announcing .NET 4.7.1 Tools for the Cloud) is out of date. There is no clientId and clientSecret properties on the AzureKeyVaultConfigBuilder class.



          There is a connectionString property however. Details on how to build that connection string when running locally are in this article: Service-to-service authentication to Azure Key Vault using .NET.



          This is the method that worked for me:



          RunAs=App;AppId={AppId};TenantId={TenantId};AppKey={ClientSecret}


          All three of these values (AppId, TenantId and AppKey) are available in the application's AD entry in Azure.






          share|improve this answer












          The documentation linked in the linked article (Announcing .NET 4.7.1 Tools for the Cloud) is out of date. There is no clientId and clientSecret properties on the AzureKeyVaultConfigBuilder class.



          There is a connectionString property however. Details on how to build that connection string when running locally are in this article: Service-to-service authentication to Azure Key Vault using .NET.



          This is the method that worked for me:



          RunAs=App;AppId={AppId};TenantId={TenantId};AppKey={ClientSecret}


          All three of these values (AppId, TenantId and AppKey) are available in the application's AD entry in Azure.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Nov 20 at 11:23









          beaudetious

          1,38532454




          1,38532454












          • Glad to see you have solved problem, it seems that mine is not well considered.
            – Joey Cai
            Nov 22 at 2:22




















          • Glad to see you have solved problem, it seems that mine is not well considered.
            – Joey Cai
            Nov 22 at 2:22


















          Glad to see you have solved problem, it seems that mine is not well considered.
          – Joey Cai
          Nov 22 at 2:22






          Glad to see you have solved problem, it seems that mine is not well considered.
          – Joey Cai
          Nov 22 at 2:22














          up vote
          0
          down vote













          I could reproduce your problem in local with the following code:



          <add name="AzureKeyVault"
          mode="Strict"
          vaultName="MyVaultName"
          type="Microsoft.Configuration.ConfigurationBuilders.AzureKeyVaultConfigBuilder, Microsoft.Configuration.ConfigurationBuilders.Azure" />


          If your application is running on an Azure service that has , this is all you need to read configuration from the vault and add it to your application. Conversely, if you are not running on a service with MSI, you can still use the vault by adding the following attributes:



          clientId – the Azure Active Directory application key that has access to your key vault.



          clientSecret – the Azure Active Directory application secret that corresponds to the clientId



          I test with following code and it works well, you could refer to it.



          <configSections>
          <section name="configBuilders" type="System.Configuration.ConfigurationBuildersSection, System.Configuration, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" restartOnExternalChanges="false" requirePermission="false" />
          </configSections>
          <configBuilders>
          <builders>
          <add name="KeyVault" mode="Strict" prefix="conn_" stripPrefix="true"
          clientId="MyId" clientSecret="mySecret" vaultName="MyVault"
          type="Microsoft.Configuration.ConfigurationBuilders.AzureKeyVaultConfigBuilder, Microsoft.Configuration.ConfigurationBuilders.Azure" />
          </builders>
          </configBuilders>


          For more details, you could refer to this article.






          share|improve this answer





















          • I have read that article as well and looking at the source code, there is no clientId or clientSecret properties for AzureKeyVaultConfigBuilder: github.com/aspnet/MicrosoftConfigurationBuilders/blob/master/…
            – beaudetious
            Nov 20 at 11:06















          up vote
          0
          down vote













          I could reproduce your problem in local with the following code:



          <add name="AzureKeyVault"
          mode="Strict"
          vaultName="MyVaultName"
          type="Microsoft.Configuration.ConfigurationBuilders.AzureKeyVaultConfigBuilder, Microsoft.Configuration.ConfigurationBuilders.Azure" />


          If your application is running on an Azure service that has , this is all you need to read configuration from the vault and add it to your application. Conversely, if you are not running on a service with MSI, you can still use the vault by adding the following attributes:



          clientId – the Azure Active Directory application key that has access to your key vault.



          clientSecret – the Azure Active Directory application secret that corresponds to the clientId



          I test with following code and it works well, you could refer to it.



          <configSections>
          <section name="configBuilders" type="System.Configuration.ConfigurationBuildersSection, System.Configuration, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" restartOnExternalChanges="false" requirePermission="false" />
          </configSections>
          <configBuilders>
          <builders>
          <add name="KeyVault" mode="Strict" prefix="conn_" stripPrefix="true"
          clientId="MyId" clientSecret="mySecret" vaultName="MyVault"
          type="Microsoft.Configuration.ConfigurationBuilders.AzureKeyVaultConfigBuilder, Microsoft.Configuration.ConfigurationBuilders.Azure" />
          </builders>
          </configBuilders>


          For more details, you could refer to this article.






          share|improve this answer





















          • I have read that article as well and looking at the source code, there is no clientId or clientSecret properties for AzureKeyVaultConfigBuilder: github.com/aspnet/MicrosoftConfigurationBuilders/blob/master/…
            – beaudetious
            Nov 20 at 11:06













          up vote
          0
          down vote










          up vote
          0
          down vote









          I could reproduce your problem in local with the following code:



          <add name="AzureKeyVault"
          mode="Strict"
          vaultName="MyVaultName"
          type="Microsoft.Configuration.ConfigurationBuilders.AzureKeyVaultConfigBuilder, Microsoft.Configuration.ConfigurationBuilders.Azure" />


          If your application is running on an Azure service that has , this is all you need to read configuration from the vault and add it to your application. Conversely, if you are not running on a service with MSI, you can still use the vault by adding the following attributes:



          clientId – the Azure Active Directory application key that has access to your key vault.



          clientSecret – the Azure Active Directory application secret that corresponds to the clientId



          I test with following code and it works well, you could refer to it.



          <configSections>
          <section name="configBuilders" type="System.Configuration.ConfigurationBuildersSection, System.Configuration, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" restartOnExternalChanges="false" requirePermission="false" />
          </configSections>
          <configBuilders>
          <builders>
          <add name="KeyVault" mode="Strict" prefix="conn_" stripPrefix="true"
          clientId="MyId" clientSecret="mySecret" vaultName="MyVault"
          type="Microsoft.Configuration.ConfigurationBuilders.AzureKeyVaultConfigBuilder, Microsoft.Configuration.ConfigurationBuilders.Azure" />
          </builders>
          </configBuilders>


          For more details, you could refer to this article.






          share|improve this answer












          I could reproduce your problem in local with the following code:



          <add name="AzureKeyVault"
          mode="Strict"
          vaultName="MyVaultName"
          type="Microsoft.Configuration.ConfigurationBuilders.AzureKeyVaultConfigBuilder, Microsoft.Configuration.ConfigurationBuilders.Azure" />


          If your application is running on an Azure service that has , this is all you need to read configuration from the vault and add it to your application. Conversely, if you are not running on a service with MSI, you can still use the vault by adding the following attributes:



          clientId – the Azure Active Directory application key that has access to your key vault.



          clientSecret – the Azure Active Directory application secret that corresponds to the clientId



          I test with following code and it works well, you could refer to it.



          <configSections>
          <section name="configBuilders" type="System.Configuration.ConfigurationBuildersSection, System.Configuration, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" restartOnExternalChanges="false" requirePermission="false" />
          </configSections>
          <configBuilders>
          <builders>
          <add name="KeyVault" mode="Strict" prefix="conn_" stripPrefix="true"
          clientId="MyId" clientSecret="mySecret" vaultName="MyVault"
          type="Microsoft.Configuration.ConfigurationBuilders.AzureKeyVaultConfigBuilder, Microsoft.Configuration.ConfigurationBuilders.Azure" />
          </builders>
          </configBuilders>


          For more details, you could refer to this article.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Nov 20 at 5:38









          Joey Cai

          4,065129




          4,065129












          • I have read that article as well and looking at the source code, there is no clientId or clientSecret properties for AzureKeyVaultConfigBuilder: github.com/aspnet/MicrosoftConfigurationBuilders/blob/master/…
            – beaudetious
            Nov 20 at 11:06


















          • I have read that article as well and looking at the source code, there is no clientId or clientSecret properties for AzureKeyVaultConfigBuilder: github.com/aspnet/MicrosoftConfigurationBuilders/blob/master/…
            – beaudetious
            Nov 20 at 11:06
















          I have read that article as well and looking at the source code, there is no clientId or clientSecret properties for AzureKeyVaultConfigBuilder: github.com/aspnet/MicrosoftConfigurationBuilders/blob/master/…
          – beaudetious
          Nov 20 at 11:06




          I have read that article as well and looking at the source code, there is no clientId or clientSecret properties for AzureKeyVaultConfigBuilder: github.com/aspnet/MicrosoftConfigurationBuilders/blob/master/…
          – beaudetious
          Nov 20 at 11:06


















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.





          Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


          Please pay close attention to the following guidance:


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53383511%2fwhat-does-the-connectionstring-attribute-look-like-in-azurekeyvault-configuratio%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          404 Error Contact Form 7 ajax form submitting

          How to know if a Active Directory user can login interactively

          Refactoring coordinates for Minecraft Pi buildings written in Python