MicrosoftSo ArcBox is really cool and I like the idea - however I'm experiencing some issues in that when spinning up the IT Pro version in an MSDN Subscription via Terraform. I have to use Eastus or eastus2 despite being in the UK as on the MSDN subscriptions only AMD processors are available so no support for nested Hyper-V
1. Doesn't create the Azure Bastion - in fact as far as I can see the Terraform code doesn't have reference to Azure Bastion
2 . The Linux Servers aren't added to AzureArc
3. Something is strange with the way the update management is setup - it picks up that patches are missing yet the update agent readiness is Not configured on all the Windows boxes
If you look at the Automation Account and Update Management it selects creating a Log Analytics workspace and enabling the solution.
However I can see the solution is enabled in Log Analytics and the Servers are connected.
Yet due to agent not being connected you can't schedule/install any updates via Arc or Automation it either errors out or is not available.
Please let me know if I'm missing something?
N.B. I've also tried via the Portal and hit the same errors.
Thanks
Paul
**** UPDATE ****
Figured out the issue the scripted Log Analytics is created in the same region this needs to be recreated in the linked location so eastus2 to eastus etc.
Automation account pointed to the new log analytics and solutions installed.
The the clients need to be repointed to the new workspace then it works
