Merge pull request #108600 from dominicbetts/central-geographies

Update IoT Central geographies

Author: PRMerger18

articles/iot-central/core/howto-create-and-manage-applications-csp.md

@@ -69,22 +69,14 @@ If you don't have an Azure subscription, you can create one in the Microsoft Par
 
 To learn more, see [Azure subscriptions](https://docs.microsoft.com/azure/guides/developer/azure-developer-guide#understanding-accounts-subscriptions-and-billing).
 
-## Region
+## Location
 
-Choose the region or [geography](https://azure.microsoft.com/global-infrastructure/geographies/) where you'd like to create your Azure IoT Central Application. Typically, you should choose the region that's closest physically to your devices to get optimal performance.
-
-To learn more, see [Azure regions](https://azure.microsoft.com/global-infrastructure/regions/) and [Azure geographies](https://azure.microsoft.com/global-infrastructure/geographies/).
-
-You can see the regions in which Azure IoT Central is available on the [Products available by region](https://azure.microsoft.com/global-infrastructure/services/?products=iot-central) page.
-
-> [!Note]
-> Once you choose a region, you cannot later move your application to a different region.
+**Location** is the [geography](https://azure.microsoft.com/global-infrastructure/geographies/) where you'd like to create the application. Typically, you should choose the location that's physically closest to your devices to get optimal performance. Currently, you can create an IoT Central application in the **Australia**, **Asia Pacific**, **Europe**, **United States**, **United Kingdom**, and **Japan** geographies. Once you choose a location, you can't later move your application to a different location.
 
 ## Application template
 
 Choose the application template you want to use for your application.
 
-
 ## Next steps
 
 Now that you have learned how to create an Azure IoT Central application as a CSP, here is the suggested next step:

articles/iot-central/core/howto-manage-iot-central-from-cli.md

@@ -51,7 +51,7 @@ These commands first create a resource group in the east US region for the appli
 | Parameter         | Description |
 | ----------------- | ----------- |
 | resource-group    | The resource group that contains the application. This resource group must already exist in your subscription. |
-| location          | By default, this command uses the location from the resource group. Currently, you can create an IoT Central application in the **Australia**, **Asia Pacific**, **Europe**, or **United States** geographies. |
+| location          | By default, this command uses the location from the resource group. Currently, you can create an IoT Central application in the **Australia**, **Asia Pacific**, **Europe**, **United States**, **United Kingdom**, and **Japan** geographies. |
 | name              | The name of the application in the Azure portal. |
 | subdomain         | The subdomain in the URL of the application. In the example, the application URL is https://mysubdomain.azureiotcentral.com. |
 | sku               | Currently, you can use either **ST1** or **ST2**. See [Azure IoT Central pricing](https://azure.microsoft.com/pricing/details/iot-central/). |

articles/iot-central/core/howto-manage-iot-central-from-portal.md

@@ -36,8 +36,7 @@ Fill in all the fields in the form. This form is similar to the form you fill ou
 
 ![Create IoT Central form](media/howto-manage-iot-central-from-portal/image6a.png)
 
-**Location** is the [geography](https://azure.microsoft.com/global-infrastructure/geographies/) where you'd like to create your application. Typically, you should choose the location that's physically closest to your devices to get optimal performance. Azure IoT Central is currently available in the **United States**, **Australia**, **Asia Pacific**, or in **Europe**.  Once you choose a location, you can't move your application to a different location later.
-
+**Location** is the [geography](https://azure.microsoft.com/global-infrastructure/geographies/) where you'd like to create your application. Typically, you should choose the location that's physically closest to your devices to get optimal performance. Azure IoT Central is currently available in the **Australia**, **Asia Pacific**, **Europe**, **United States**, **United Kingdom**, and **Japan** geographies. Once you choose a location, you can't move your application to a different location later.
 
 After filling out all fields, select **Create**.
 

articles/iot-central/core/howto-manage-iot-central-from-powershell.md

@@ -64,7 +64,7 @@ The script first creates a resource group in the east US region for the applicat
 |Parameter         |Description |
 |------------------|------------|
 |ResourceGroupName |The resource group that contains the application. This resource group must already exist in your subscription. |
-|Location |By default, this cmdlet uses the location from the resource group. Currently, you can create an IoT Central application in the **Australia**, **Asia Pacific**, **Europe**, or **United States** geographies.  |
+|Location |By default, this cmdlet uses the location from the resource group. Currently, you can create an IoT Central application in the **Australia**, **Asia Pacific**, **Europe**, **United States**, **United Kingdom**, and **Japan** geographies. |
 |Name              |The name of the application in the Azure portal. |
 |Subdomain         |The subdomain in the URL of the application. In the example, the application URL is https://mysubdomain.azureiotcentral.com. |
 |Sku               |Currently, you can use either **ST1** or **ST2**. See [Azure IoT Central pricing](https://azure.microsoft.com/pricing/details/iot-central/). |

articles/iot-central/core/overview-iot-central.md

@@ -34,7 +34,7 @@ This article outlines, for IoT Central:
 - Jobs don't support complex types.
 - Array schema types aren't supported.
 - Only the C device SDK and the Node.js device and service SDKs are supported.
-- It's only available in the United States, Europe, Asia Pacific, and Australia locations.
+- It's only available in the United States, Europe, Asia Pacific, Australia, United Kingdom, and Japan locations.
 - Device capability models must have all the interfaces defined inline in the same file.
 - Support for [IoT Plug and Play](../../iot-pnp/overview-iot-plug-and-play.md) is in preview and is only supported only in selected regions.
 
@@ -69,7 +69,6 @@ This device template includes:
 - Cloud properties that aren't stored on the device.
 - Customizations, dashboards, and forms that are part of your IoT Central application.
 
-
 ### Pricing
 
 You can create IoT Central application using a 7-day free trial, or use a standard pricing plan.