Azure Stack


Azure Stack is Microsoft’s Azure Cloud for on-premises environments. Azure Stack contains the core Azure services, allowing organizations to take advantage of Azure’s offerings with the security, compliance, and financial benefits of hosting it in their own data-centers.

  • Virtual Machine Provisioning

  • Backups / Snapshots

  • Resource Group Sync & Selection

  • Network Sync & Selection

  • Security Group Sync & Selection

  • Storage Account Sync & Selection

  • Marketplace Search and Provisioning

  • Remote Console

  • Periodic Synchronization

  • Lifecycle Management and Resize

  • Availability Set Support

  • Azure Load Balancers

  • Azure Storage

  • Docker Host Provisioning & Management

  • Service Plan Sync

  • Pricing Sync with markup options

  • Cost Estimator

Combine these features with public Azure and Morpheus can provide a single pane of glass and self service portal for managing instances scattered across both Azure offerings.


Azure Stack Accessibility

By default, the Azure Stack management url’s are not accessible from an external network. Port mappings and DNS must be configured for communication between the Morpheus Appliance and Azure Stack.


In order to communicate with Azure Stack, Morpheus must be able to reach the internal Azure Stack network. The Azure Stack Portal needs to be exposed to the Morpheus Appliances’ network with corresponding entries added to DNS.

One option to expose the Internal Azure Stack network to the Morpheus Appliances network is to use the Expose-AzureStackPortal.ps1 powershell script from An Azure Stack Port Mapping Tool is also available.

Below is a sample output from the script for reference:

[Admin Portal] Created port mappings on to
[Admin Portal] Ports: 13011 30015 13001 13010 13021 13020 443 13003 12646 12647 12648 12649 12650 12495 13026 12499
[Admin Portal] DNS: - adminportal.local.azurestack.external adminmanagement.local.azurestack.external

[Tenant Portal] Created port mappings on to
[Tenant Portal] Ports: 13011 30015 13001 13010 13021 13020 443 13003 12646 12647 12648 12649 12650 12495 13026 12499
[Tenant Portal] DNS: - portal.local.azurestack.external management.local.azurestack.external

[Blob Storage] Created port mappings on to
[Blob Storage] Ports: 80 443
[Blob Storage] DNS:  *.blob.local.azurestack.external

VERBOSE: DNS delegation/forwarding is optional, change the DNS records on MAS-DC01 manually (dnsmgmt.msc from Host).
[DNS Delegation] Created port mappings on to
[DNS Delegation] Ports: 53 (TCP/UDP)
[DNS Delegation] DNS: local.azurestack.external NS
[DNS Delegation] Change records on MAS-DC01 manually `if` you plan to use DNS forwarding.
[DNS Delegation] Change records back to the original internal IPs before running this script again.

VERBOSE: App Service detected and external IPs specified, creating mappings.
[App Service API] Created port mappings on to
[App Service API] Ports: 443
[App Service API] DNS:  api.appservice.local.azurestack.external
[App Service Apps] Created port mappings on to
[App Service Apps] Ports: 80 443 21 990
[App Service Apps] DNS:  *.appservice.local.azurestack.external

Azure Stack Resources

The following resources need to be created and configured inside Azure Stack for successful provisioning:

  • Resource Group(s)

  • Virtual Network(s)

  • Storage Account(s)

  • Network Security Group(s)

    • Inbound ports open from Morpheus Appliance: 22, 5985, 3389

    • Outbound ports open to Morpheus Appliance: 80, 443


Proper Network and Network Security Group configuration is required for Morpheus agent install, communication, and remote console access. Other configurations, such as docker instances, will need the appropriate ports opened as well.

Required Credentials & Permissions

Credentials to integrate Morpheus with Azure Stack are located in both the public Azure Portal and the Private Azure Stack Portal. The Azure Active Directory Application used must be an owner of the Azure Stack subscription.

Azure Portal:
  • Azure Active Directory Application Credentials

  • Directory ID

  • Management URL

  • Identity Resource URL

  • Application ID

  • Key Value

Azure Stack Portal:
  • Azure Stack Subscription ID

  • Active Directory App from Azure portal added as owner of the Azure Stack Subscription in Azure Stack.

Adding an Azure Stack Cloud


  1. In the Morpheus UI, navigate to Infrastructure > Clouds and Select + CREATE CLOUD

  2. Select AZURE STACK (PRIVATE) from the Clouds list and select NEXT

  3. In the Configure section, enter:

    Cloud Configuration


    Name of the Cloud in Morpheus


    Unique code used for api/cli, automation and policies.


    Description field for adding notes on the cloud, such as location.


    For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.


    If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.


    When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.


    When enabled, Morpheus will maintain the expected power state of managed VMs. Morpheus will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by Morpheus) to ensure availability of services.


    When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in Morpheus. This setting is not applicable to discovered/unmanaged resources.




    Azure AD Azure Stack Administrator app or Microsoft Azure Stack Administrator app url. Example: https://adminmanagement.local.azurestack.external/


    Azure AD Azure Stack Administrator App ID URI Example:


    This should match the base domain in your Management url. Example: local.azurestack.external


    Subscription ID from Azure Stack portal (this is different from the Subscription ID in you Azure portal used when configuring Azure Stack)


    This is the Directory ID from the Azure AD directory


    Application ID of Azure AD app with Azure Stack permissions granted, and has been added as an owner of the Azure Stack subscription (in the Azure Stack portal).


    Key Value of Application ID used above


    Once all credentials are entered and validated, the Location and Resource Group fields will populate.


    Select an Azure Stack region for the cloud to scope to. This typically will be “local”.

    Resource Group

    Select All or a single Resource Group to scope the cloud to. Selecting a single Resource Group will only sync resources in that Resource Group and disable Resource Group selection during provisioning. All will sync all resources and allow specifying the Resource Group during provisioning.

    Inventory Existing Instances

    If enabled, existing Virtual Machines will be inventoried and appear as unmanaged Virtual Machines in Morpheus.

  4. The Azure Stack cloud is ready to be added to a group and saved. Additional configuration options available:


    All fields and options can be edited after the Cloud is created.

    Advanced Options


    Specify a default domain for instances provisioned to this Cloud.


    Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.


    Alternate Appliance url for scenarios when the default Appliance URL (configured in admin > settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.


    Configures the time zone on provisioned VM’s if necessary.


    Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.


    Unmanaged or select a Network Integration (NSX, ACI etc)


    On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)


    Security Server setting is for Security Service Integrations such as ACI


    Select Internal (Morpheus) or an existing Trust Provider Integration


    Single Disk, LVM or Clustered


    Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution


    Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration


    Enable Guidance recommendations on cloud resources.


    Enable for Morpheus to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.


    Records for instances provisioned in this cloud will be added to selected DNS integration.


    Services for instances provisioned in this cloud will be added to selected Service Registry integration.


    Select a Chef, Ansible or Puppet integration to be used with this Cloud.


    Select CMDB Integration to automatically update selected CMDB.


    When checked, any automatically discovered (unmanaged) servers onboarded into Morpheus from this Cloud will also have CMDB records created for them.


    Select an existing Change Management Integration to set on the Cloud. ex: Cherwell

    • SSH / WINRM: Morpheus will use SSH or WINRM for Agent install.

    • Cloud Init / Unattend (when available): (DEFAULT) Morpheus will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. Morpheus will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.


    Set a proxy for outbound communication from the Morpheus Appliance to the Cloud endpoints. Proxies can be added in the Infrastructure > Networks > Proxies tab.


    Enable to have Agent Installation on by default for all provisioning into this Cloud. Disable for Agent Installation to be off by default for all provisioning into this Cloud.


    When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the Morpheus dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.


    Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:

    • Service Plans

    • Resource Pools

    • Networks

    • Security Groups

    • Datastores

    • Folders

    Provisioning Command


    Set a proxy for inbound communication from Instances to the Morpheus Appliance. Proxies can be added in the Infrastructure > Networks > Proxies tab.

    Bypass Proxy for Appliance URL

    Enable to bypass proxy settings (if added) for Morpheus Agent communication to the Appliance URL.


    Include a list of IP addresses or name servers to exclude from proxy traversal


    Add cloud-init user data. Morpheus 4.1.0 and earlier assumes bash syntax. Morpheus 4.1.1 and later supports all User Data formats. Refer to for more information.

  5. Once all options are configured, select NEXT to add the cloud to a Group.


    A Group must be specified or created for the new Cloud to be added to. Clouds can be added to additional Groups or removed from Groups after being created.


    Add the new Cloud to an exiting Group in Morpheus .


    Creates a new Group in Morpheus and adds the Cloud to the Group.

  6. Confirm all settings are correct and select COMPLETE. The Azure Stack Cloud will be added, and Morpheus will perform the initial cloud sync of:

    • Virtual Machines (if Inventory Existing Instances is enabled)

    • Networks

    • Virtual Images/Blueprints

    • Network Security Groups

    • Storage Accounts

    • Marketplace Catalog

    • Availability Sets


    Synced Networks can be configured or deactivated from the Networks section in this Clouds detail page, or in the Infrastructure > Networks section.