Validate graph integration for Azure Stack Hub

Use the Azure Stack Hub Readiness Checker tool (AzsReadinessChecker) to validate that your environment is ready for graph integration with Azure Stack Hub. Validate graph integration before you begin datacenter integration or before an Azure Stack Hub deployment.

The readiness checker validates:

  • The credentials to the service account created for graph integration have appropriate rights to query Active Directory.
  • The global catalog can be resolved and is contactable.
  • The KDC can be resolved and is contactable.
  • Necessary network connectivity is in place.

For more information about Azure Stack Hub datacenter integration, see Azure Stack Hub datacenter integration - Identity.

Get the readiness checker tool

Download the latest version of the Azure Stack Hub Readiness Checker tool (AzsReadinessChecker) from the PowerShell Gallery.


The following prerequisites must be in place.

The computer where the tool runs:

  • Windows 10 or Windows Server 2016 with domain connectivity.
  • PowerShell 5.1 or later. To check your version, run the following PowerShell command and then review the Major version and Minor versions:
  • Active Directory PowerShell module.
  • Latest version of the Microsoft Azure Stack Hub Readiness Checker tool.

Active Directory environment:

  • Identify the username and password for an account for the graph service in the existing Active Directory instance.
  • Identify the Active Directory forest root FQDN.

Validate the graph service

  1. On a computer that meets the prerequisites, open an administrative PowerShell prompt and then run the following command to install the AzsReadinessChecker:

    Install-Module Microsoft.AzureStack.ReadinessChecker -Force -AllowPrerelease
  2. From the PowerShell prompt, run the following command to set the $graphCredential variable to the graph account. Replace contoso\graphservice with your account by using the domain\username format.

    $graphCredential = Get-Credential contoso\graphservice -Message "Enter Credentials for the Graph Service Account"
  3. From the PowerShell prompt, run the following command to start validation for the graph service. Specify the value for -ForestFQDN as the FQDN for the forest root.

    Invoke-AzsGraphValidation -ForestFQDN -Credential $graphCredential
  4. After the tool runs, review the output. Confirm that the status is OK for graph integration requirements. A successful validation is similar to the following example:

    Testing Graph Integration (v1.0)
            Test Forest Root:            OK
            Test Graph Credential:       OK
            Test Global Catalog:         OK
            Test KDC:                    OK
            Test LDAP Search:            OK
            Test Network Connectivity:   OK
    [-] In standalone mode, some tests should not be considered fully indicative of connectivity or readiness the Azure Stack Hub Stamp requires prior to Datacenter Integration.
    Additional help URL:
    AzsReadinessChecker Log location (contains PII): C:\Users\username\AppData\Local\Temp\AzsReadinessChecker\AzsReadinessChecker.log
    AzsReadinessChecker Report location (contains PII): C:\Users\username\AppData\Local\Temp\AzsReadinessChecker\AzsReadinessCheckerReport.json
    Invoke-AzsGraphValidation Completed

In production environments, testing network connectivity from an operator's workstation isn't fully indicative of the connectivity available to Azure Stack Hub. The Azure Stack Hub stamp's public VIP network needs the connectivity for LDAP traffic to perform identity integration.

Report and log file

Each time validation runs, it logs results to AzsReadinessChecker.log and AzsReadinessCheckerReport.json. The location of these files appears with the validation results in PowerShell.

The validation files can help you share status before you deploy Azure Stack Hub or investigate validation problems. Both files persist the results of each subsequent validation check. The report gives your deployment team confirmation of the identity configuration. The log file can help your deployment or support team investigate validation issues.

By default, both files are written to C:\Users\<username>\AppData\Local\Temp\AzsReadinessChecker\.


  • -OutputPath: The path parameter at the end of the run command to specify a different report location.
  • -CleanReport: The parameter at the end of the run command to clear AzsReadinessCheckerReport.json of previous report information. For more information, see Azure Stack Hub validation report.

Validation failures

If a validation check fails, details about the failure appear in the PowerShell window. The tool also logs information to AzsGraphIntegration.log.

Next steps

View the readiness report
General Azure Stack Hub integration considerations