Steps to deploy IDP image to Azure VM

    Applies to:
  • SecureAuth Identity Platform
  • Legacy SecureAuth IdP
Deployment model:
  • Cloud
  • Hybrid
  • On Premises
  • Version Affected:  [All versions]


    How to deploy SA IDP image to Azure VM?


    Azure doesn't support Dynamic Disks. If you have dynamic VHDs, first convert the VHDs to Fixed using the below cmdlet:

    Convert-VHD -Path <source_path> -DestinationPath <destination_path> -VHDType Fixed
    1. Upload the Fixed size VHDs to Azure storage account.
    2. Create Azure managed disks with Source blob set to the VHD files in the storage account.

    3. To create the image in Azure, create the below resources:
      • Create Azure Image Gallery
      • Create Image Definition in the Azure Image Gallery. Make sure OS state is set to Specialized.
      • Create Image Version in the Image Definition. (Use the Managed Disks created in step 3 to create Image Version)
    4. Create a VM using the image version. This image version can be used to deploy other IDPs

    5. Once the the VM is deployed
      • Changed drive letter of temp drive from D to T.
      • If the disk attached as the second (data) disk is offline, use Disk Management to bring it online and assign the drive letter D to it.
      • Copy all the files from T to D drive, except the MFCApp_bin folder, as it must already have MFCApp_bin and Scripts folders in it.
      • Run "D:\MFCApp_Bin\InstallCerts\CertInstaller.exe" and "D:\MFCApp_Bin\FirstStartup.cmd"

    6. Run the IDP setup utility.

    Special Considerations:  

    • All the Azure resources created in Step 1 - Step 3, must be created in the same region.
    • If you are using Disk Encryption Sets to encrypt your disks, it must be in the same region as of your disks.

    SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

    Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.

    0 out of 0 found this helpful



    Please sign in to leave a comment.