Azure Stack Hub datacenter integration walkthrough
This article describes the end-to-end process for Azure Stack Hub datacenter integration, from purchasing to post-deployment support. The integration is a collaborative project between the customer, a solution provider, and Microsoft. Click the following tabs to see the specific steps for each member of the project, and see the next sections for a summary of different phases for the project timeline.
- Describe use cases and requirements
- Determine the billing model
- Review and approve contracts
- Complete the Deployment Worksheet
- Make sure deployment prerequisites are met
- Prepare the datacenter
- Provide subscription info during deployment
- Resolve any questions about the provided data
Microsoft or an Azure Stack Hub solution partner will help evaluate your goals. They'll help you decide questions like:
- Is Azure Stack Hub the right solution for your organization?
- What type of billing and licensing model will work for your organization?
- What size solution will you need?
- What are the power and cooling requirements?
Use the Azure Stack Hub Capacity Planner to investigate and analyze the best hardware capacity and configuration for your needs.
Your organization commits to purchasing Azure Stack Hub, signs contracts and purchase orders, and provides the integration requirements data to the solution provider.
You decide how to integrate Azure Stack Hub into your datacenter. Microsoft collaborated with solution providers to publish a deployment worksheet to help you gather the necessary information. The general datacenter integration considerations article provides information that helps you complete the template, known as the Deployment Worksheet.
All prerequisites are investigated before ordering the solution 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.
Licensing model. The licensing model options for you to choose from depend on the kind of deployment you'll have. Your identity provider choice has no bearing on tenant virtual machines or the identity system and accounts they use.
Customers that are in a disconnected deployment have only one option: capacity-based billing.
Customers that are in a connected deployment can choose between capacity-based billing and pay-as-you-use. Capacity-based billing requires an Enterprise Agreement (EA) Azure Subscription for registration. This is necessary for registration, which provides for the availability of items in Azure Marketplace through an Azure Subscription.
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.
After all the pre-requisite information is gathered through the deployment worksheet, the solution provider will kick off the factory process based on the data collected to ensure a successful integration of Azure Stack Hub into your datacenter.
Changes that require re-deployment
The following table lists changes to your Azure Stack Hub deployment that require re-deploying the entire system:
|Change identity system from Azure AD to AD FS||Yes|
|Change the Azure AD directory that was used for deployment||Yes|
|Change the network IP ranges||Yes|
|Change the AD FS integrated Active Directory||No|
|Change the billing model||No|
|Change the Azure subscription used for registration||No|
Your solution provider will work with you on scheduling when the solution will arrive to your facility. Once received and put in place, you'll need to schedule time with the solution provider to have an engineer come onsite to perform the Azure Stack Hub deployment.
It's crucial that all prerequisite data is locked and available before the onsite engineer arrives to deploy the solution.
All certificates must be purchased and ready.
Region name must be decided on.
All network integration parameters are finalized and match with what you have shared with your solution provider.
If any of this information has changed, make sure to communicate the change with the solution provider before you schedule the actual deployment.
To deploy Azure Stack Hub, an onsite engineer from your hardware solution provider will need to be present to kick off the deployment. To ensure a successful deployment, ensure that all information provided through the deployment worksheet hasn't changed.
The following checks are what you should expect from the onsite engineer during the deployment experience:
- Check all the cabling and border connectivity to ensure the solution is properly put together and meets your requirements.
- Configure the solution Hardware Lifecycle Host (HLH), if present.
- Check to make sure all BMC, BIOS, and network settings are correct.
- Make sure firmware for all components is at the latest approved version by the solution.
- Start the deployment.
A deployment procedure by the onsite engineer might take about one business week to complete.
Several steps must be performed by the partner before the solution is handed off to the customer in the post-integration phase. In this phase, validation is important to ensure the system is deployed and performing correctly.
Actions that should be taken by the OEM Partner are:
Register with Azure.
Back up 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.
There are several steps that are required or optional depending on the installation type.
If deployment was completed using AD FS, then the Azure Stack Hub stamp will need to be integrated with customer's own AD FS.
This step is the responsibility of the customer, although the partner may optionally choose to offer services to do this.
Integration with an existing monitoring system from the respective partner.
System Center Operations Manager Integration also supports fleet management capabilities.
Azure Stack Hub enables an Azure-consistent, integrated support experience that covers the full system lifecycle. To fully support Azure Stack Hub integrated systems, customers need two support contracts: one with Microsoft (or their Cloud Solution Provider) for Azure services support and one with the hardware provider for system support. The integrated support experience provides coordinated escalation and resolution so that customers get a consistent support experience no matter whom they call first. For customers who already have Premier, Azure -Standard / ProDirect or Partner support with Microsoft, Azure Stack Hub software support is included.
The integrated support experience makes use of a Case Exchange mechanism for bi-directional transfer of support cases and case updates between Microsoft and the hardware partner. Microsoft Azure Stack Hub will follow the Modern Lifecycle policy.
Learn more about general datacenter integration considerations.
Submit and view feedback for