This article describes the end-to-end process for Azure Stack Hub datacenter integration, from purchasing to post-deployment. The integration is a collaborative project between the customer and Microsoft. The following sections cover different phases for the project timeline and specific steps for project members.
The following table depicts what can be expected during the various phases of deployment.
|Order Process||Pre-Deployment||Integration, Validation, Transport||Onsite Deployment||Post-Deployment|
|Microsoft||- Signal to delivery to US location
- Azure Stack Hub ruggedized = 10 Days
|Provide required tooling and documentation to collect datacenter requirements||- Validate configuration artifacts and check validation results
- Ensure hardware is delivered
|- Rack and stack
- Network integration
- Azure Stack Hub deployment
- Hand off to customer
|Registration and Marketplace syndication|
|Customer||Signals purchase||- Fills out network details in deployment worksheet
- Collects certificates
- Obtains Azure AD accounts
- Runs any validation tooling provided
|Ensure the site is ready with network, power, cooling prerequisites||- Be prepared with deployment configuration artifacts
- Customer’s network engineer available
Your organization will work with Microsoft to place an order for an allocated number of systems. Once you place the order, Microsoft will have 10 days to deliver the Azure Stack Hub ruggedized to your US location. Microsoft will ensure that all secure supply chain requirements are met.
Billing starts 14 days after the hardware has shipped.
To create an Azure Stack Hub resource, take the following steps in the Azure portal.
Use your Microsoft Azure credentials to sign in to the Azure portal at this URL: https://portal.azure.com.
In the left-pane, select + Create a resource. Search for and select Azure Stack Hub ruggedized. Select Create.
Pick the subscription that you want to use for the Azure Stack Hub device. Select the country to where you want to ship this physical device. Select Show devices.
A short form is displayed. Fill out the form and select Submit. Microsoft will enable your subscription.
After the subscription is enabled, you should be able to able to proceed with the resource creation. In the Select device type blade, choose Select.
On the Basics tab, enter or select the following Project details.
Setting Value Subscription This is automatically populated based on the earlier selection. Subscription is linked to your billing account. Resource group Select an existing group or create a new group.
Enter or select the following Instance details.
Setting Value Name A friendly name to identify the resource.
The name has between 2 and 50 characters containing letter, numbers, and hyphens.
Name starts and ends with a letter or a number.
Region For a list of all the regions where the Azure Stack Hub resource is available, see Azure products available by region. If using Azure Government, all the government regions are available as shown in the Azure regions.
Choose a location closest to the geographical region where you want to deploy your device.
Select Next: Shipping address.
If you already have a device, select the combo box for I have a Azure Stack Hub device.
If this is the new device that you are ordering, enter the contact name, company, address to ship the device, and contact information.
Select Next: Review + create.
The resource creation takes a few minutes. After the resource is successfully created and deployed, you're notified. Select Go to resource.
After the order is placed, Microsoft reviews the order and reaches out to you (via email) with shipping details.
You decide how to integrate Azure Stack Hub into your datacenter. Microsoft has published a deployment worksheet that guides you through gathering all necessary information needed to integrate successfully into your datacenter. In addition, a certain set of certificates are required at time of deployment. To help you obtain these certificates, Microsoft provides you a tool called the Azure Stack Hub Readiness Checker. This tool will help you create Certificate Signing Requests (CSRs) to provide to your internal CA.
All prerequisites are validated to help prevent deployment delays. Verifying prerequisites can take time and require coordination and data gathering from different departments within your organization.
You'll choose the following items:
- Azure Stack Hub connection model and identity provider. You can choose to deploy Azure Stack Hub either connected to the internet (and to Azure) or disconnected. To get the most benefit from Azure Stack Hub, including hybrid scenarios, you'd want to deploy connected to Azure. Choosing Active Directory Federation Services (AD FS) or Azure Active Directory (Azure AD) is a one-time decision that you must make at deployment time. You can't change your identity provider later without redeploying the entire system.
- Network integration. Network integration is crucial for deployment, operation, and management of Azure Stack Hub systems. There are several considerations that go into ensuring the Azure Stack Hub solution is resilient and has a highly available physical infrastructure to support its operations.
- Firewall integration. It's recommended that you use a firewall to help secure Azure Stack Hub. Firewalls can help prevent DDOS attacks, intrusion detection, and content inspection. However, it should be noted that it can become a throughput bottleneck for Azure storage services.
- Certificate requirements. It's critical that all required certificates are available before an onsite engineer arrives at your datacenter for deployment.
Once all the pre-requisite information is gathered through the deployment worksheet, Microsoft will ensure that we verify all validation tools have been run and assist with any further questions that you may have.
Microsoft will work with you to ensure all required hardware arrives at the US Location within the allocated time given.
It's crucial that all prerequisite data is locked and available before the onsite Microsoft deployment engineer arrives to deploy the solution.
- Deployment Worksheet has all data filled out.
- All certificates must be validated and ready.
- Region name must be decided on.
- All network integration parameters are finalized.
If any of this information has changed, make sure to work with your internal organization to ensure the information is updated prior to the arrival of the onsite deployment engineer. This will prevent any delays in the deployment process.
To deploy Azure Stack Hub, a Microsoft deployment engineer will be present to kick off the deployment. We require that a Network Engineer from your organization also be available during the period of the onsite deployment.
The following checks are what you should expect from the onsite engineer during the deployment experience:
- Unboxing and inventory of hardware
- Connecting power and powering on the solution
- Validating physical hardware health
- Check all the cabling and border connectivity to ensure the solution is properly put together and meets your requirements.
- Configure the solution HLH (Hardware Lifecycle Host).
- Datacenter network integration
- Check to make sure all physical hardware settings are correct.
- Make sure firmware for all components is at the latest approved version by the solution.
- Start the deployment.
Several steps must be performed by the Microsoft deployment engineer before the solution is handed off to the customer. In this phase, validation is important to ensure the system is deployed and performing correctly.
Actions that should be taken by the Microsoft deployment engineer:
- Enable value-add resource providers (RPs).
- Run test-azurestack.
- Registration with Azure.
- Marketplace syndication.
- Backup switch configuration and HLH configuration files.
- Prepare a customer summary for deployment.
- Check updates to make sure the solution software is updated to the latest version.
Learn more about steps to install and configure Microsoft Azure Stack Hub Rugged.