Cannot deploy Install-AzSKOrganizationPolicy with App insights location set... about devopskit

[VishalHaibatpure]

Please use below parameter set for customized setup for Org Policy.

Install-AzSKOrganizationPolicy -SubscriptionId <SUBID> -OrgName "<ORG-DEPT NAME>" -StorageAccountName "<storagename>" -ResourceGroupLocation westeurope -AppInsightLocation westeurope -MonitoringDashboardLocation westeurope -ResourceGroupName "<NAME>" -AppInsightName "<NAME>" -PolicyFolderPath "<C: PATH>"

[Stoffe]

Then, I get the same error as before...

Have you actually tried that commandline? or do I have a strange version? (Just downloaded it last week)

Install-AzSKOrganizationPolicy : Parameter set cannot be resolved using the specified named parameters.
At line:1 char:1

• Install-AzSKOrganizationPolicy -SubscriptionId 097edece-e071-4747-a27 ...

•   + CategoryInfo          : InvalidArgument: (:) [Install-AzSKOrganizationPolicy], ParameterBindingException
    + FullyQualifiedErrorId : AmbiguousParameterSet,Install-AzSKOrganizationPolicy
  

[VishalHaibatpure]

The given parameter set works for me with version 3.5.0
Make sure you are not using "-DepartmentName" in your command. That is the only parameter not supported for custom resources setup for Org policy.

If this is not helping out, you can try executing command using PowerShell ISE command window

[Stoffe]

Ahh, ok, didnt know the DepartmentName was not suppose to be on, ok, however now I get another error...

InvalidArgument: Only alphanumeric characters are supported in StorageAccountName param. And length should be less than 24 characters

And, I tried to have 1 letter, 3 letters, 10 letters and one number in the storageaccount name, and even tried to remove characters from other parameters to a minimum to make sure the error message is relevant...

ok more testing show that a numbers only in storage account works, hmm, I am however doubtful that this is a problem for AzSK maybe this is a problem connected to the Azure side instead after reading up on others having the same problem

However, giving the storageaccount a name of for instance 123456, gives me an error:

The storage account named 123456 is already taken. Parameter name: Name Failed to create storage account [123456]

[VishalHaibatpure]

It should work with unique alphanumeric name as storage account names are scoped globally across subscriptions.

[VishalHaibatpure]

@Stoffe : Let us know if issue is resolved for you.

[njohnso]

Found a solution to @Stoffe problem. In case others have the same issue. If you receive the error:

InvalidArgument: Only alphanumeric characters are supported in StorageAccountName param. And length should be less than 24 characters

You are using uppercase letters. Use all lowercase letters and this will work fine. Suggested a solution here:

#966