Create Key Vault Error
Closed this issue · 7 comments
First I got error for using 'USGov Virginia' then change this in the script to use the suggested 'usgovvirginia'
Now getting:
No registered resource provider found for location 'usgovvirginia' and API version '2018-02-14-preview' for type 'vaults'. The supported api-versions are '2015-06-01, 2016-10-01'. The supported locations are 'usgovvirginia, usgoviowa, usdodcentral, usdodeast, usgovtexas, usgovarizona'.
Can't get passed this error, any suggestions or updates? I do have a Govt Azure Subscription or how to change the Azure API verision used?
Can you provide any additional context for when you're encountering this error? Please check that the Microsoft.KeyVault resource provider is registered in your Azure Gov subscription. You can do this through the Azure portal under Cost Management + Billing > Subscriptions > Resource providers:
I did turn on Microsoft.KeyVault, now showing "registered" unfortunately the same error below. This error occurs running the predeployment script "Orchestration_InitialSetup.ps1" when [Key Vault Resource] name is create. Then it fails with the below error in Powershell.
Module Version Reference In Powershell:
Script 5.0.0 AzureRM.KeyVault {Add-AzureKeyVaultCertificate, Update-AzureKeyVaultCertificate, Stop-AzureKeyVaultCertificateOperation, Get-AzureKeyVaultCertificateOperation...}
I'm going to try Import-Module -Name AzureRM older version
for an API version it's asking for in the error. That's the only thing I can see so far that's an obvious thing to try next. I am going to have to determine somehow where version number matches the dates supplied. :(
No registered resource provider found for location 'USGov Virginia' and API version '2018-02-14-preview' for type 'vaults'. The supported api-versions are '2015-06-01, 2016-10-01'. The supported locations are 'usgovvirginia, usgoviowa, usdodcentral, usdodeast, usgovtexas, usgovarizona'.
An error has occurred in the pre-deployment orchestration setup. Please review any error messages before attempting a re-deployment.
Please let me know if that approach is successful. It looks like the RP in Azure Gov does not support the 2018-02-14-preview API version.
Yeah!!!, I figured it out..
I attempted version 5.7.0 since latest version of AzureRM 6.1? is a preview:
Reference:
https://github.com/Azure/azure-powershell/releases/tag/v5.7.0-April2018
Verified using the specified AzureRM before predeployment
Name Version Path
AzureRM 5.7.0 C:\Program Files\WindowsPowerShell\Modules\AzureRM\5.7.0\AzureRM.psd1
Made it through, received "Orchestration Complete"
So the bug has something to do using the latest version of AzureRM when you do a "Install-Module -Name AzureRM" from the instructions, the version installed is the "preview" seen in the above errors that has the issue with the KeyVault Api. Hope this helps anyone else.
If I have time later, I can come in and contribute or fork to help add a AzureRM Version. The ApiVersion seems to be a show stopper.
Note: I also went through to make sure any subscription resources you had registered in your screenshot was "registered" additional to just the KeyVault.
Thanks jomolesk for your contribution and feedback.
@jomolesk
Thank you for the feedback as well, I'll work to make sure this issue gets addressed.