Deploy Azure Stack On An Azure VM (Part 2)

Share This Post

Share on facebook
Share on linkedin
Share on twitter
Share on email

Post-Installation Configuration Contd (Approx 1 hour 20 mins)

  • Follow the instructions on this link to register Azure Stack with the Azure market place
    • https://docs.microsoft.com/en-us/azure/azure-stack/asdk/asdk-register
      • For the Azure AD login in the instructions here, use your normal Azure AD admin account and not the Azure AD user account that you created earlier (as this account does not have the necessary permissions)
      • For the “AzureStack\CloudAdmin” account, use the same password as the local administrator password
      • Download “Ubuntu Server 16.04 LTS” image from Azure (Approx 1 hour)

Deploy a Test VM (Approx 2 hours)

a. Create a PLAN, and an OFFER that can be used for deployments

  • Do this from the Admin Portal
  • Create a PLAN (with services and quotas)
    • Admin Portal → Plans → Add
    • Display Name: Virtual-Machines1
    • Resource Group: Create new
    • Resource Group Name: RG-OffersAndPlans1
    • Services: Select these three services – Microsoft.Compute, Microsoft.Network and Microsoft.Storage
    • Quotas: Accept default Quotas for all three services
  • Create an OFFER
    • Admin Portal → Offers → Add
    • Display Name: Virtual Machines1
    • Provider Subscription: Default Provider Subscription
    • Resource Group: Use existing
    • Resource Group Name: RG-OffersAndPlans1
    • Base plans: virtual-machines1

b. Set the offer state to “public”

  • Do this from the Admin Portal
  • In the Offers blade, click virtual-machines1
  • Under “Settings” –> “Offer settings“, change “Accessibility State” to “Public
  • Click “Save

c. Subscribe to the OFFER

  • Do this from the Tenant Portal
  • Open an incognito browser window
  • Type https://portal.local.azurestack.external and then press Enter
  • In the Sign in dialog, in Username box type the Azure AD Global Admin credential that you used during the setup (doazurestack@whatever.onmicrosoft.com)
  • Type the Password
  • Click Sign in
  • In the Microsoft Azure Stack User Portal that opens navigate to More Services, and click on Subscriptions
  • In the Subscriptions blade, click Add
  • In the Get a Subscription blade that opens click Select an Offer
  • In the Choose an Offerpage that opens click Virtual Machines1
  • Click Create and then click Refresh
  • Click More Services and then click Subscriptions to confirm

d. Deploy a test VM

Other Useful Information

a. Connect to your Azure Stack using PowerShell
# Replace <AZURE_AD_GLOBAL_ADMIN_PASSWORD> with the password of your Azure AD Global Admin
# Replace "<AZURE_AD_TENANT>" with the username of your Azure AD Global Admin E.g. "doazurestack@whatever.onmicrosoft.com"
# Replace "<AZURE_AD_GLOBAL_ADMIN>" with the username of your Azure AD Global Admin E.g. "doazurestack@whatever.onmicrosoft.com"
Import-Module C:\AzureStack-Tools-master\Connect\AzureStack.Connect.psm1
$Password = ConvertTo-SecureString "<AZURE_AD_GLOBAL_ADMIN_PASSWORD>" -AsPlainText -Force
Add-AzureRmEnvironment -Name AzureStack -ArmEndpoint https://management.local.azurestack.external
$TenantID = Get-AzsDirectoryTenantID -AADTenantName "<AZURE_AD_TENANT>" -EnvironmentName AzureStack
$Cred = New-Object System.Management.Automation.PSCredential("<AZURE_AD_GLOBAL_ADMIN>",$Password)
Login-AzureRmAccount -EnvironmentName "AzureStack" -TenantId $TenantID -Credential $Cred

b. Verify and select subscription

Get-AzureRmSubscription
Get-AzureRmLocation
$subscriptionid = (Get-AzureRmSubscription -SubscriptionName 'Virtual Machines1').SubscriptionId
Select-AzureRMSubscription -SubscriptionID $Subscriptionid

 

Subscribe To Our Newsletter

Get updates and learn from the best

More To Explore

Uncategorized

New Azure Container Instance Vulnerability — What to do?

Just yesterday, Microsoft disclosed a new (and yet to be clarified) Azure Container Instance vulnerability — https://msrc-blog.microsoft.com/2021/09/08/coordinated-disclosure-of-vulnerability-in-azure-container-instances-service/. From the information shared in the disclosure, it seems

Protecting against #ChaosDB

Cloud security researchers @sagitz and @nirohfeld who both work at Wiz recently discovered what I think is a major vulnerability that exploits the recent CosmosDB Jupyter notebook feature to

Do You Want To Boost Your Business?

drop us a line and keep in touch