Google Cloudでデータを保護するために使用する鍵。デフォルトでは、 Google Cloud は Google が管理する暗号鍵を使用して、保存されているデータを自動的に暗号化します。データを保護する鍵について特定のコンプライアンスや規制の要件がある場合、顧客管理の暗号鍵（CMEK）を使用して保存データの暗号化と復号を行うことができます。これらの暗号鍵は、ユーザーによって作成、管理、所有されます。
注: 設定した暗号鍵は、このソースで作成されるすべてのリソースに使用されます。
省略可: 移行リソースのユーザータグ
Migrate to Virtual Machines サービスは、VM ディスクのスナップショットを作成して Google Cloudに移行します。
これらのリソースにカスタムタグを関連付ける場合は、ここで指定します。これにより、Azure 環境で Migrate to Virtual Machines によって作成されたすべてのリソースを識別できるようになります。スナップショットには、スナップショットで説明したタグも含まれています。
[[["わかりやすい","easyToUnderstand","thumb-up"],["問題の解決に役立った","solvedMyProblem","thumb-up"],["その他","otherUp","thumb-up"]],[["わかりにくい","hardToUnderstand","thumb-down"],["情報またはサンプルコードが不正確","incorrectInformationOrSampleCode","thumb-down"],["必要な情報 / サンプルがない","missingTheInformationSamplesINeed","thumb-down"],["翻訳に関する問題","translationIssue","thumb-down"],["その他","otherDown","thumb-down"]],["最終更新日 2025-09-04 UTC。"],[],[],null,["# Create an Azure source\n\n[Migrate to Virtual Machines](/migrate/virtual-machines)\nlets you migrate your Azure virtual machines (VMs) from your Azure account\nto Compute Engine instances.\n\nPrerequisites\n-------------\n\n- [Enable the **VM Migration API**](https://console.cloud.google.com/apis/library/vmmigration.googleapis.com) on your host project.\n- Review the [supported operating systems](/migrate/virtual-machines/docs/5.0/discover/supported-os-versions) that support migrating VMs from an Azure source.\n- Review [Migrating VMs with Migrate to Virtual Machines: Getting started](/migrate/virtual-machines/docs/5.0/discover/migrating-vms-migrate-for-compute-engine-getting-started) documentation. This document provides insight into the overall structure of Migrate to Virtual Machines, including important concepts and reference information that helps you migrate your workload efficiently and effectively.\n\nMigration limitations from Azure\n--------------------------------\n\nMigrate to Virtual Machines does not support migration of VMs with the following\nattributes:\n\n- Ephemeral OS disks\n- Non-managed disks\n\nAttempting a migration of a VM with such disks will fail with an appropriate\nerror message.\n\nAlso note that due to their nature - temporary disks data is not guaranteed to\nbe migrated with the VM and won't persist following the creation of a clone VM\nor a cutover VM.\n\nMigrate your workload from an Azure source\n------------------------------------------\n\nBefore initiating your migration with Azure as a source, set up your Azure\nenvironment by completing the following tasks:\n\n1. [Register your app](#register-your-app) in the Azure portal.\n2. [Create a custom role](#create-a-custom-role) to be accessed by the Migrate to Virtual Machines service.\n3. [Assign the custom role to an app](#assign-custom-role-to-app).\n4. [Create an Azure source](#create-an-azure-source) using Google Cloud.\n\n### Register your app\n\nTo register your app, follow these steps:\n\n1. In the Azure portal, go to the **App Registration** page, and click **New registration**.\n2. To add new client credentials, click **Add a certificate or secret**.\n3. To add a new client secret, click **+ New client secret** and enter a description and expiry date for the client secret.\n4. Click **Add**.\n\nYour client secret is now ready. Make sure to copy your client secret value. You\nwill need it later when you set up the source.\n\n### Create a custom role\n\nTo migrate your Azure workload, [create a custom role](https://learn.microsoft.com/en-us/azure/role-based-access-control/custom-roles) and assign it to the app you registered in the\n[Register your app](#register-your-app) step.\n\nTo create a custom role, use the following steps:\n\n1. In the Azure portal, go to the [Subscriptions](https://portal.azure.com/#view/Microsoft_Azure_Billing/SubscriptionsBlade) page and select your Azure subscription.\n2. Copy the **Subscription ID** by clicking on it.\n3. Save following JSON template and replace \u003cvar translate=\"no\"\u003eSUBSCRIPTION_ID\u003c/var\u003e\n with the **Subscription ID** you copied in Step 2:\n\n \u003cbr /\u003e\n\n ```\n {\n \"properties\": {\n \"roleName\": \"Minimum M2VM permissions role\",\n \"description\": \"This role contains the bare minimum of Azure IAM permissions to support M2VM flow\",\n \"assignableScopes\": [\n \"/subscriptions/SUBSCRIPTION_ID\"\n ],\n \"permissions\": [\n {\n \"actions\": [\n \"Microsoft.Resources/subscriptions/resourceGroups/write\",\n \"Microsoft.Resources/subscriptions/resourceGroups/read\",\n \"Microsoft.Resources/subscriptions/resourceGroups/delete\",\n \"Microsoft.Compute/virtualMachines/read\",\n \"Microsoft.Compute/virtualMachines/write\",\n \"Microsoft.Compute/virtualMachines/deallocate/action\",\n \"Microsoft.Compute/disks/read\",\n \"Microsoft.Compute/snapshots/delete\",\n \"Microsoft.Compute/snapshots/write\",\n \"Microsoft.Compute/snapshots/beginGetAccess/action\",\n \"Microsoft.Compute/snapshots/read\",\n \"Microsoft.Compute/snapshots/endGetAccess/action\"\n ],\n \"notActions\": [],\n \"dataActions\": [],\n \"notDataActions\": []\n }\n ]\n }\n }\n \n ```\n\n \u003cbr /\u003e\n\n For more information about the permission details, see [permission details](/migrate/virtual-machines/docs/5.0/reference/roles-reference#permissions_to_configure_azure_as_a_source).\n4. In the Azure portal, go to the **Access control (IAM)** page.\n\n5. To add a custom role, click **+ Add**.\n\n6. Click **Start from JSON** and then click **Select file** to upload the JSON\n file you created in Step 3.\n\n7. To review your inputs click **Review + Create** , and then to create the\n custom role click **Create**.\n\n### Assign the custom role to an app\n\nTo assign a custom role to an app, follow these steps:\n\n1. In the Azure portal, go to the **Access control (IAM)** page.\n2. Click **+ Add** and then click **Add role assignment**.\n3. Search for the custom role you created in [Create a custom role](#create-a-custom-role) by typing `m2vm`, and select it.\n4. Click **Next**.\n5. Click **+ Select members** and search for the app name you registered in [Register your app](#register-your-app) and click **Select**.\n6. To review and assign the custom role to your app, click **Review + Assign**.\n\n### Create an Azure source\n\nAfter you have registered your app, added your secret, and set its permissions,\ncreate an Azure source in the Migrate to Virtual Machines service.\n\nTo create an Azure source, follow these steps:\n\n1. In the Google Cloud console, go to the [Migrate to Virtual Machines](https://console.cloud.google.com/compute/mfce/dashboard) page.\n2. Select the **Sources** tab.\n3. From the **Add source** list, select **+ Add Azure source**.\n4. Enter your source details on the **Create Azure source** panel.\n\n | **Caution:** You cannot edit the **GCP region** or **Azure location** fields after creating your source. If you need to edit these fields, we recommend that you wait 24 hours before revoking the credentials you replaced in order to not interrupt an ongoing replication cycle.\n\n The following table describes the parameters for Azure source details.\n\n5. Click **Create**. A notice detailing your new source appears.\n\n6. Wait (up to 15 minutes but usually less) until the **Source status** is\n indicated as **Active**.\n\nCheck your inventory to verify that there are instances that correspond to the\ntags (and/or security groups) that you specified when you created your source.\n\nAs part of source creation, your project is automatically added as a target\nproject.\n\n#### Cloud sources limitations\n\nYou can host a maximum of 15 cloud sources (AWS sources, Azure sources, or both\nthe sources combined) on a host project at a time. For example, you can host 10\nAWS sources and 5 Azure sources on a host project at a time. Conversely, you\ncan host 7 AWS sources and 8 Azure sources on a host project at a time. If you\nwant to add a new cloud source to a project that already hosts 15 cloud\nsources, you must delete an existing source, and then add the new source. You\ncan also try using a different project to host the new cloud source if you\ndon't want to delete any existing sources.\n\n### Next steps: Start your migration\n\nAfter you've created an Azure source, you are ready to start your migration. The\nrest of the process for migrating your workload from an Azure source matches the\nprocess for other sources for Migrate to Virtual Machines.\n\nFor details on how to start your migration process, see\n[Migrating individual VMs](/migrate/virtual-machines/docs/5.0/migrate/migrating-vms).\n\nDifferences from using VMware as a source\n-----------------------------------------\n\nThere are several unique aspects about using Azure as a source for your migrations:\n\n- You can create and edit an Azure source from the UI.\n- There is no utilization report for an Azure source.\n\nDifferences from using AWS as a source\n--------------------------------------\n\nThe usage is almost identical to the usage of AWS as a source."]]
