Azure to Azure Migration

Due to mergers, acquisitions or sale it’s likely that companies develop a need to migrate key services from platform to platform. Although it is currently possible to migrate resources between subscriptions it is not possible to migrate across tenants natively. The below covers the steps required to migrate tenant to tenant using MigAZ a community tool availble from GitHub (covering ARM to ARM migration) https://github.com/Azure/migAz Pre-reqs Windows 8 or higer Latest PowerShell AzureRM module Install-Module -Name AzureRM -AllowClobber Import-Module -Name AzureRM Separate “Owner” role accounts for both tenants The resource being migrated should be powered off & any active connections removed Disk encryption using ADE v1. Continue reading

Removing ADE v1.1

Azure Disk Encryption leverages BitLocker to provide full disk encryption on Azure virtual machines running Windows. This solution is integrated with Azure Key Vault to manage disk encryption keys and secrets in your key vault subscription. There are two versions of extension schema for Azure Disk Encryption (ADE): v2.2 - A newer recommended schema that does not use Azure Active Directory (AAD) properties. v1.1 - An older schema that requires Azure Active Directory (AAD) properties. Continue reading

Configuring a Routable Domain

Clients wishing to migrate to Office365 will usually utilise Azure Active Directory Connect to form part of the migration, this will synchronise Active Directory to Azure to be used throughout the Office365 suite. Previously it was best practise to append domain names with .local or similar as routable domains were not previously required. Synchronising users with non-routable suffix’s will fail generating alerts and the users will not be synchronised. Prior to migration its possible to highlight the risk using Microsoft’s IDFix tool found here. Continue reading

Rename Azure VM with Powershell

Changes happen and sometimes there is a requirement to change the name of a virtual machine, be it from an error or a change of naming convention internally. Natively within Azure there is currently no way to rename a virtual machine, its virtual network or the disks attached too it, forcing users to either give up on name changes or build out new virtual machines and migrate disks. Whilst there are some scripts available already that run through the process these did not meet my specific needs, primarily of retaining the internal private IP address. Continue reading