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.