Microsoft Defender for IoT
General

Move an iotSecuritySolutions Resource to Another Region by using the Azure Portal

In brief

The article now consistently uses the iotSecuritySolutions resource name, updates metadata and wording, and streamlines the Azure portal, Log Analytics, verification, and cleanup instructions.

What Defender admins need to know

Administrators using this procedure should follow the revised terminology and steps; no required action is stated.

Summaries are generated from the documentation change itself.

Documentation change

The comparison below shows only the changed extract. Use the full-page view for complete context.

Move an "iotsecuritysolutions"iotSecuritySolutions resource to another region by using the Azure portal

There are various scenarios for moving an existing resource from one region to another. For example, you might want to take advantage of features, and services that are only available in specific regions, to meet internal policy and governance requirements, or in response to capacity planning requirements.

You can move a Microsoft Defender for IoT "iotsecuritysolutions"iotSecuritySolutions resource to a different Azure region. The "iotsecuritysolutions"iotSecuritySolutions resource is a hidden resource that is connected to a specific IoT hub resource that is used to enable security on the hub. Learn how to configure, and create the "iotsecuritysolutions"iotSecuritySolutions resource.

Resource prerequisites

  • Make sure that the resource is in the Azure region that you want to move from.

  • An existing "iotsecuritysolutions"iotSecuritySolutions resource.

  • Make sure that your Azure subscription allows you to create "iotsecuritysolutions"iotSecuritySolutions resources in the target region.

  • Make sure that your subscription has enough resources to support the addition of resources for this process. For more information, see Azure subscription and service limits, quotas, and constraints

Prepare alerts before moving the resource

Prepare the "iotsecuritysolutions"iotSecuritySolutions resource for the region move by locating it and confirming its current region.

Before transitioning the resource to the new region, we recommend that you create a Log Analytics workspace to preserve your existing alerts and raw events. A Log Analytics workspace provides a central location to retain this dataexisting alerts and raw events so that it remainsthey remain available after the move.

To find the resource you want to move:move:

  1. Sign in to the Azure portal, and then select All Resources.

  2. Select Show hidden types.

Move the IoT Hub to another region

The hidden "iotsecuritysolutions"iotSecuritySolutions resource is tied to its associated IoT Hub, so moving the resource to another region requires cloning the IoT Hub to the target region. To clone the IoT Hub and its linked "iotsecuritysolutions"iotSecuritySolutions resource, follow the instructions in Clone and migrate an IoT Hub to another region.

After the IoT Hub move is complete and Defender for IoT is re-enabled onenabled, reconnect the destination hub, you can reconnect ithub to the Log Analytics workspace that you configured before the move.set up earlier.

Verify the moved resource in the target region

After the move, verify that the "iotsecuritysolutions"iotSecuritySolutions resource is in the target region, that the Defender for IoT connection to the IoT Hub is enabled, and that recommendations are working correctly.

To verify the resource is in the correct region:region:

  1. Sign in to the Azure portal, and then select All Resources.

  2. Select Show hidden types.

    :::image type="content" source="media/region-move/location-changed.png" alt-text="Screenshot that shows you the region your hub is located in.":::

To ensure everything is working correctly:correctly:

  1. Navigate to IoT Hub > Your hub > Defender for IoT, and select Recommendations.

Clean up source resources

Don’Don't clean up until you have've finished verifying that the resource has moved,moved and the recommendations have transferred. When you're ready, clean up the old resources by performing these steps:

  • Deleting the old hub removes all active devices from the hub. If you haven't already, delete the old hub.

  • If you have routing resources that you moved to the new location, you can delete the old routing resources.

Next steps

In this tutorial, you moved an Azure resource from one region to another and cleaned up the source resource.