You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -1246,6 +1250,8 @@ The data object has the following properties:
1246
1250
|`contentType`| string | The content type specified for the blob. |
1247
1251
|`contentLength`| integer | The size of the blob in bytes. |
1248
1252
|`blobType`| string | The type of blob. Valid values are either "BlockBlob" or "PageBlob". |
1253
+
|`accessTier`| string | The target tier of the blob. Appears only for the event BlobTierChanged. |
1254
+
|`previousTier`| string | The source tier of the blob. Appears only for the event BlobTierChanged. If the blob is inferring the tier from the storage account, this field will not appear. |
1249
1255
|`contentOffset`| number | The offset in bytes of a write operation taken at the point where the event-triggering application completed writing to the file. <br>Appears only for events triggered on blob storage accounts that have a hierarchical namespace.|
1250
1256
|`destinationUrl`|string | The url of the file that will exist after the operation completes. For example, if a file is renamed, the `destinationUrl` property contains the url of the new file name. <br>Appears only for events triggered on blob storage accounts that have a hierarchical namespace.|
1251
1257
|`sourceUrl`|string | The url of the file that exists before the operation is done. For example, if a file is renamed, the `sourceUrl` contains the url of the original file name before the rename operation. <br>Appears only for events triggered on blob storage accounts that have a hierarchical namespace. |
Copy file name to clipboardExpand all lines: articles/migrate/tutorial-migrate-physical-virtual-machines.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Migrate machines as physical servers to Azure with Azure Migrate and Modernize
3
3
description: This article describes how to migrate physical machines to Azure with Azure Migrate and Modernize.
4
-
author: vijain
4
+
author: pingvishal-msft
5
5
ms.author: vijain
6
6
ms.manager: kmadnani
7
7
ms.topic: tutorial
@@ -199,7 +199,7 @@ Now, select machines for migration.
199
199
200
200
:::image type="content" source="./media/tutorial-migrate-physical-virtual-machines/select-vms-inline.png" alt-text="Screenshot that shows selecting VMs." lightbox="./media/tutorial-migrate-physical-virtual-machines/select-vms-expanded.png":::
201
201
202
-
1. In **Target settings**, select the subscription and target region to which you'll migrate. Specify the resource group in which the Azure VMs will reside after migration.
202
+
1. In **Target settings**, select the subscription to which you'll migrate. (The region is set to your selection in the previous step and can't be modified.) Specify the resource group in which the Azure VMs will reside after migration.
203
203
1. In **Virtual Network**, select the Azure virtual network/subnet to which the Azure VMs will be joined after migration.
204
204
1. In **Cache storage account**, keep the default option to use the cache storage account that's automatically created for the project. Use the dropdown list if you want to specify a different storage account to use as the cache storage account for replication. <br/>
0 commit comments