Subscription Creation

Potentially outdated

This page was last updated 14 months ago (on 2025-01-22). Verify the information is still accurate before relying on it.

When creating a new subscription we require the assistance of IT, this is mostly down to Rhapsody Health not having an enterprise agreement with Microsoft. This should change in the near future to allow team members with the correct level of access to add a subscription without entering any card details.

Once a new subscription is added, depending on its purpose we should move it to the correct management group, this will cover the subscription with azure policy rules which helps us to set guardrails against the environment.

Non IAC Modifications

Encryption @ Host

Enable host encryption at the subscription level. We currently enable host encryption using Azure CLI, for more information on how to do this please take a look here: https://learn.microsoft.com/en-us/azure/virtual-machines/disks-enable-host-based-encryption-portal

Azure Policy

Currently Azure policy prevents the creation of a Azure VNET and Subnet without the creation of a network security group. If this allowed to enforce our current Terraform code will fail, to negate this control we can apply a exemption for the subscription we are attempting to deploy into.

• Access the subscription from the Azure portal

* Open the “policies ” page on the subscription.

* Now add an “exemption ” on the subscription for the policy “Subnets should have a Network Security Group ”.