Register your Azure Stack HCI cluster with reduced permissions

Arpita Duppala thanks for the ACK, VERY much appreciated 

BUT sorry ,

I again have to express my concern about the quality and embracement customers expect from Microsoft regarding products and services, and here I also think about Support which is getting worse and worse . . . 

If I rewind to the time frame where Windows 2000 were released (Active Directory) and the accompanied Recourse Kit.

On the shelf it took almost 1,5 m and the technical details included here were amazing, we are a lot of "silverback's" that want this to reappear!

We miss the quality and the deep technical description, PLEASE bring it back, PLEASE!!!!!

Documentation here https://docs.microsoft.com/ is so superficial, that it is almost useless, sorry!

MarkRussinovich , we miss your whitepapers, deep dive on Windows, Case of the Unexplained, explanations of Scheduling algorithm on NUMA vs. non NUMA, etc.

I (Maybe I'm the lonely rider?) want the technical quality back as delivered in the Windows Internals classes and books, that you and David Solomon provided   "PLEASE COME BACK"  , , , , , ,  and show the way to describe things, so we, the customers, understands it and get the opportunity to get the best out of the technology the Microsoft provides.

Right now we are fighting to implement workarounds, waiting for the next release, that may (or may not) solve the issue.

Also deploying CU every month without description of all included fixes to e.g. AzHCI, how should we, the customers, be able to prove we have change management, we can't.

-Ib

IbTornoe : Sorry for the inconvenience it has caused, currently we do not support tagging Arc RG during registration workflow. It is in our backlog to support tagging the Arc RG in future release. Thank you for your feedback.

Just to follow up on the above:

When it fails we see this.

=======================================

Write-ErrorLog : CreateResourceGroupFailed : Could not create resource group resourceId: subscriptions/77585cb5-cc1b-47a6-b60d-4c1ec4b078fc/resourceGroups/SYSHCL50-DK0-Arc. CorrelationId: 148081ec-6b6a-4d7e-ab8f-00a9cf0cbbe1 At C:\Program Files\WindowsPowerShell\Modules\Az.StackHCI\1.2.0\Az.StackHCI.psm1:2537 char:9 + Write-ErrorLog -Exception $_.Exception -Category OperationSto ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OperationStopped: (:) [Write-Error], ErrorResponseMessageException
+ FullyQualifiedErrorId : Microsoft.Azure.Commands.ResourceManager.Cmdlets.Entities.ErrorResponses.ErrorResponseMessageException,Write-ErrorLog

Write-ErrorLog : Exception occurred in Register-AzStackHCI : At C:\Program Files\WindowsPowerShell\Modules\Az.StackHCI\1.2.0\Az.StackHCI.psm1:2492 char:35
+ ... $arcres = New-AzResource -ResourceId $arcResourceId -ApiVersion $HC ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
At C:\Program Files\WindowsPowerShell\Modules\Az.StackHCI\1.2.0\Az.StackHCI.psm1:2542 char:9
+ Write-ErrorLog ("Exception occurred in Register-AzStackHCI : ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OperationStopped: (:) [Write-Error], WriteErrorException
+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Write-ErrorLog

=======================================

The line to pay attension to is this:

Write-ErrorLog : Exception occurred in Register-AzStackHCI : At C:\Program Files\WindowsPowerShell\Modules\Az.StackHCI\1.2.0\Az.StackHCI.psm1:2492 char:35

Lookin in the Az.StackHCI.psm1 at line 2492 we see

$arcres = New-AzResource -ResourceId $arcResourceId -ApiVersion $HCIArcAPIVersion -PropertyObject $arcInstanceResourceGroup -Force

And NO parsing on of Tags.

We have temporarily disabled the Policy that requires Tags on RG's and then the Register-AzStackHCI ran through and created the RG for Arc

Just tried to register a AzHCI Cluster today.

After a lot of issues we are now stuck where Register-AzStackHCI are creating the RG for Arc.

We have a Policy that requires Tags to be created, but it seems that Register-AzStackHCI does not use the Tags configured on the commandline, and it is not supported to pre-create this RG

From documantation:

If you want to specify the name of the Arc for server resource group, use the additional parameter -ArcServerResourceGroupName <ArcRgName>. Note that the specified <ArcRgName> cannot pre-exist, it must be created by the HCI service.

E.G.

Register-AzStackHCI -SubscriptionId "1111111-1111-1111-1111-111111111111" -ComputerName Server1 -Tag @{AvailabilityHours= "4" ; Criticality= "Critical" ; EnvironmentType = "p" ; FinancialWorkPackageId = "12345" ; owner = "XYZ"}

So we are in a sort of catch22 situation here . . . .