Registering to Azure

Heggli, Helge 6 Reputation points
2020-09-28T08:42:57.09+00:00

Hi, in my PoC im trying to configure the connection towards azure. The PoC is running on an isolated environment in Azure, but our azure accounts have conditional access settings (i cant change) that require signins to be from our network. Im trying to figure out the way to go around this, Register-AzStackHCI has the parameters 

    [[-ArmAccessToken] <String>]
    [[-GraphAccessToken] <String>]
    [[-AccountId] <String>]

would these be from my account? or can i precreate the appregistration and use these? if so how to get these two tokens?

Azure Stack HCI
Azure Stack HCI
A hyperconverged infrastructure operating system delivered as an Azure service that provides security, performance, and feature updates.
273 questions

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Declan Turley 1 Reputation point
    2020-11-05T02:21:04.763+00:00

    I just got mine registered. Log into one of the cluster nodes and run:
    Register-AzStackHCI -SubscriptionId 'subID' -Region 'East US'
    Region should be East US or West Europe.

  2. Matt McSpirit 11 Reputation points MVP
    2020-11-06T20:31:15.187+00:00

    Hi all -

    @Heggli, Helge - The parameters you've identified are primarily designed for integration with Windows Admin Center, and while it could be possible to use them to circumvent your conditional access settings, they don't tell the whole story - the AzSHCI nodes themselves still talk to Azure and so while you may overcome the initial hurdle, your conditional access settings may still block that node to Azure communication.

    The best advice here, if possible, would be either to create a separate test tenant in AAD, perhaps in a Visual Studio subscription, or a free trial, or alternatively, think about using a S2S or Point to Site VPN to extend your corporate network/local device to securely communicate with your POC environment in Azure, and thus meet your conditional access settings.

    @Declan Turley - the suggestion to use the latest module is the right one - there was an issue with V0.3.0 of the Azure Stack HCI module, and the issue should be resolved in the latest module versions.

    0 comments