If you choose the
Disconnect from Azure option, you can deploy and
use Microsoft Azure Stack Hub without a connection to the Internet. Choose this
option if you:
Have security or other
restrictions that require you to deploy Azure Stack Hub in an environment that
is not connected to the Internet.
Want to block data
(including usage data) from being sent to Azure.
Want to use Azure Stack Hub
purely as a private-cloud solution that is deployed to your corporate intranet,
and are not interested in hybrid scenarios.
Table 1. Options that are based on physical connectionOptions that are based on physical connection
Options
Physically disconnected
Physically connected
Billing
Must be capacity
Enterprise agreements (EA) only
Capacity or consumption
EA or Cloud Solution Provider (CSP)
Identity store
Must be ADFS
AAD or ADFS
Marketplace syndication
Not applicable
Supported
“Bring your own” licensing of syndicated images
Registration
Not applicable
Automated
Patch and update
Required, requires removable media and a separate connected
device
Automated
NOTE: A physically disconnected environment is sometimes known as a
“submarine scenario.”
With a disconnected deployment, you are limited to an ADFS identity
store and a capacity-based billing model.
A disconnected deployment means that you will not have connectivity to
Azure during deployment, or you do not want to use AAD as your identity store.
However, you can later connect your Azure Stack Hub instance to Azure for
hybrid scenarios for tenant virtual machines (VMs).
If you want to have connectivity to Azure after deployment, regardless
of what you want to use as your identity store, choose the
Connect to Azure deployment option.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\