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
You can configure Azure Active Directory B2C (Azure AD B2C) so that a user who is signed in with a local account can change their password without using email verification to prove their identity.
29
+
You can configure Azure Active Directory B2C (Azure AD B2C) to allow users who are signed in with a local account to change their password without using email verification to prove their identity.
30
30
31
31
The password change flow involves the following steps:
32
32
33
33
1. The user signs in to their local account. If the session is still active, Azure AD B2C authorizes the user and skips to the next step.
34
-
1. In **Old password**, the user verifies their old password. In **New password**, they create and confirm their new password.
34
+
1. In **Old password**, the user verifies their current password. In **New password**, they create and confirm their new password.
35
35
36
36
> Ensure the Azure user account has the required Azure Migrate built-in roles to create projects, register appliances, and access discovery results. To understand the minimum role requirements, see [Azure Migrate built‑in roles](prepare-azure-accounts.md).
55
55
56
56
## Prepare VMware
57
-
You can skip this step if you are discovering VMs from your Azure VMware Solution environment. You should be able to use your AVS cloudadmin account to discover and assess servers.
57
+
You can skip this step if you are discovering VMs from your Azure VMware Solution environment. You should be able to use your [AVS cloudadmin account](/azure/azure-vmware/architecture-identity#vcenter-server-access-and-identity) to discover and assess servers.
58
58
59
59
On your on-premises vCenter Server, check that your account has [permissions](migrate-support-matrix-vmware-migration.md#vmware-vsphere-requirements-agentless) to create a VM by using a VMware Open Virtualization Appliance (OVA) virtual machine (VM) installation file. You must have these [permissions](migrate-support-matrix-vmware-migration.md#vmware-vsphere-requirements-agentless) when you deploy the Azure Migrate appliance as a VMware VM by using an OVA file.
# Migrate VMware vSphere VMs to Azure (agent-based)
16
16
17
-
This article shows you how to migrate on-premises VMware vSphere VMs to Azure, using the [Migration and modernization](migrate-services-overview.md) tool, with agent-based migration. You can also migrate VMware vSphere VMs using agentless migration (Recommended). [Compare](server-migrate-overview.md) the methods.
17
+
This article shows you how to migrate on-premises VMware vSphere or Azure VMware Solution VMs to Azure, using the [Migration and modernization](migrate-services-overview.md) tool, with agent-based migration. You can also migrate VMware vSphere VMs using agentless migration (Recommended). [Compare](server-migrate-overview.md) the methods.
18
18
19
19
In this tutorial, you learn how to:
20
20
> [!div class="checklist"]
@@ -76,7 +76,7 @@ If you are following the least privilege principle, assign the **Application Dev
76
76
77
77
### Set up an Azure network
78
78
79
-
[Set up an Azure network](/azure/virtual-network/manage-virtual-network). On-premises machines are replicated to Azure Managed Disks. When you fail over to Azure for migration, Azure VMs are created from these managed disks, and joined to the Azure network you set up.
79
+
[Set up an Azure network](/azure/virtual-network/manage-virtual-network). Source (on-premises or Azure VMware Solution) machines are replicated to Azure Managed Disks. When you fail over to Azure for migration, Azure VMs are created from these managed disks, and joined to the Azure network you set up.
80
80
81
81
82
82
## Prepare for migration
@@ -128,7 +128,7 @@ Make sure VMware vSphere VMs comply with requirements for migration to Azure.
128
128
129
129
1.[Verify](migrate-support-matrix-vmware-migration.md#vmware-vsphere-requirements-agent-based) VMware vSphere VM requirements.
130
130
2.[Verify](migrate-support-matrix-vmware-migration.md#vm-requirements-agent-based) VM requirements for migration.
131
-
3. Verify Azure settings. On-premises VMs you replicate to Azure must comply with [Azure VM requirements](migrate-support-matrix-vmware-migration.md#azure-vm-requirements).
131
+
3. Verify Azure settings. Source VMs (on-premises or Azure VMware Solution VMs) you replicate to Azure must comply with [Azure VM requirements](migrate-support-matrix-vmware-migration.md#azure-vm-requirements).
132
132
4. There are some changes needed on VMs before you migrate them to Azure.
133
133
- It's important to make these changes before you begin migration. If you migrate the VM before you make the change, the VM might not boot up in Azure.
134
134
- Review [Windows](prepare-for-migration.md#windows-machines) and [Linux](prepare-for-migration.md#linux-machines) changes you need to make.
@@ -308,15 +308,15 @@ The new simplified process follows a streamlined flow that begins with discovery
308
308
309
309
Replication occurs as follows:
310
310
- When the Start Replication job finishes successfully, the machines begin their initial replication to Azure.
311
-
- After initial replication finishes, delta replication begins. Incremental changes to on-premises disks are periodically replicated to the replica disks in Azure.
311
+
- After initial replication finishes, delta replication begins. Incremental changes to source disks (on-premises or AVS disks) are periodically replicated to the replica disks in Azure.
312
312
313
313
314
314
## Run a test migration
315
315
316
316
317
317
When delta replication begins, you can run a test migration for the VMs, before running a full migration to Azure. We highly recommend that you do this at least once for each machine, before you migrate it.
318
318
319
-
- Running a test migration checks that migration will work as expected, without impacting the on-premises machines, which remain operational, and continue replicating.
319
+
- Running a test migration checks that migration will work as expected, without impacting the source machines (on-premises or AVS machines), which remain operational, and continue replicating.
320
320
- Test migration simulates the migration by creating an Azure VM using replicated data (usually migrating to a non-production VNet in your Azure subscription).
321
321
- You can use the replicated test Azure VM to validate the migration, perform app testing, and address any issues before full migration.
322
322
@@ -339,36 +339,36 @@ Do a test migration as follows:
339
339
340
340
## Migrate VMs
341
341
342
-
After you've verified that the test migration works as expected, you can migrate the on-premises machines.
342
+
After you've verified that the test migration works as expected, you can migrate the source machine (on-premises or AVS).
343
343
344
344
1. In the Azure Migrate project > **Servers, databases and web apps** > **Migration and modernization**, select **Replicating servers**.
345
345
2. In **Replicating machines**, right-click the VM > **Migrate**.
346
346
3. In **Migrate** > **Shut down virtual machines and perform a planned migration with no data loss**, select **Yes** > **OK**.
347
-
- By default Azure Migrate shuts down the on-premises VM to ensure minimum data loss.
347
+
- By default Azure Migrate shuts down the source VM (on-premises or AVS) to ensure minimum data loss.
348
348
- If you don't want to shut down the VM, select **No**
349
349
4. A migration job starts for the VM. Track the job in Azure notifications.
350
350
5. After the job finishes, you can view and manage the VM from the **Virtual Machines** page.
351
351
352
352
## Complete the migration
353
353
354
354
1. After the migration is done, right-click the VM > **Stop replication**. This does the following:
355
-
- Stops replication for the on-premises machine.
355
+
- Stops replication for the source machine (on-premises or AVS).
356
356
- Removes the machine from the **Replicating servers** count in the Migration and modernization tool.
357
357
- Cleans up replication state information for the VM.
358
358
1. Verify and [troubleshoot any Windows activation issues on the Azure VM.](/troubleshoot/azure/virtual-machines/troubleshoot-activation-problems)
359
359
1. Perform any post-migration app tweaks, such as host names, updating database connection strings, and web server configurations.
360
360
1. Perform final application and migration acceptance testing on the migrated application now running in Azure.
361
361
1. Cut over traffic to the migrated Azure VM instance.
362
-
1. Remove the on-premises VMs from your local VM inventory.
363
-
1. Remove the on-premises VMs from local backups.
362
+
1. Remove the source (on-premises or AVS) VMs from your local VM inventory.
363
+
1. Remove the source (on-premises or AVS) VMs from local backups.
364
364
1. Update any internal documentation to show the new location and IP address of the Azure VMs.
365
365
366
366
## Post-migration best practices
367
367
368
-
- On-premises
368
+
- On-premises or on Azure VMware Solution
369
369
- Move app traffic over to the app running on the migrated Azure VM instance.
370
-
- Remove the on-premises VMs from your local VM inventory.
371
-
- Remove the on-premises VMs from local backups.
370
+
- Remove the source VMs (on-premises or AVS) from your local VM inventory.
371
+
- Remove the source VMs (on-premises or AVS) from local backups.
372
372
- Update any internal documentation to show the new location and IP address of the Azure VMs.
373
373
- Tweak Azure VM settings after migration:
374
374
- The [Azure VM agent](/azure/virtual-machines/extensions/agent-windows) manages VM interaction with the Azure Fabric Controller. It's required for some Azure services, such as Azure Backup, Site Recovery, and Azure Security. When migrating VMware VMs with agent-based migration, the Mobility Service installer installs Azure VM agent on Windows machines. On Linux VMs, we recommend that you install the agent after migration.
You can filter virtual network flow logs based on the state of a network flow. Flow state represents the lifecycle stage of a connection as observed by Network Watcher, such as when a flow begins, continues, ends, or is denied.
98
99
99
-
You can enable RecordTypes filtering during flow log creation by choosing which flow record formats to collect in order to tailor logging output without generating unnecessary data.
100
+
Use the RecordTypes parameter to specify which flow states you want to record. The parameter accepts one or more comma‑separated values.
101
+
102
+
### Supported RecordType Values
103
+
104
+
| Value | Description |
105
+
|-------|-------------|
106
+
| B | Begin: when a flow is created. No statistics are provided. |
107
+
| C | Continuing: an ongoing flow. Statistics are provided at five-minute intervals. |
108
+
| E | End: when a flow is terminated. Statistics are provided. |
109
+
| D | Deny: when a flow is denied. |
110
+
111
+
### Example scenarios using RecordTypes
112
+
113
+
| Scenario | RecordTypes value |
114
+
|----------|-------------------|
115
+
| Capture only denied traffic | "D" |
116
+
| Capture flow creation and termination events | "B,E" |
117
+
| Capture only active traffic statistics | "C" |
118
+
| Capture full flow lifecycle | "B,C,E" |
119
+
120
+
## Manage RecordTypes filtering condition
121
+
122
+
You can enable RecordTypes filtering during flow log creation by choosing which flow record formats to collect in order to tailor logging output without generating unnecessary data. You can also update RecordTypes filterning condition for an existing flow log.
100
123
101
124
```azurepowershell-interactive
102
125
# Enable RecordTypes filtering while creating flowlog
Copy file name to clipboardExpand all lines: articles/storage/blobs/storage-blob-change-feed.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -650,7 +650,7 @@ The following example shows a change event record in JSON format that uses event
650
650
651
651
```
652
652
653
-
<aid="conditions"></a>
653
+
-<aid="conditions"></a>If event publishing remains blocked for over six months due to customer configuration errors (such as `KeyVaultNotFound` or authentication failures), the events are automatically deleted and garbage‑collected.
Copy file name to clipboardExpand all lines: articles/storage/file-sync/file-sync-monitoring.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -98,14 +98,14 @@ The following metric charts are viewable in the Storage Sync Service portal:
98
98
| Agent Version Expiration Information | Number of days until the agent version expires | Storage Sync Service - Metrics |
99
99
| Bytes synced | Size of data transferred (upload and download) | Sync Group - Status, Server endpoint - Sync status, Storage Sync Service - Metrics |
100
100
| Cache data size by last access time | Size of data by last access time | Server Endpoint - Cloud Tiering Status, Storage Sync Service - Metrics |
101
-
| Cloud tiering cache hit rate | Percentage of bytes that have been served from the cache vs. recalled from the cloud | Sync Group - Status, Server Endpoint - Cloud Tiering Status, Storage Sync Service - Metrics |
101
+
| Cloud tiering cache hit rate | Percentage of bytes that have been served from the cache vs. recalled from the cloud. This metric is generated only when there is active I/O (such as file reads or recalls) on the server endpoint.| Sync Group - Status, Server Endpoint - Cloud Tiering Status, Storage Sync Service - Metrics |
102
102
| Cloud tiering low disk space mode | Status of disk space on server | Storage Sync Service - Metrics |
103
-
| Cloud tiering recall success rate | Success status of cloud tiering recall | Storage Sync Service - Metrics |
103
+
| Cloud tiering recall success rate | Success status of cloud tiering recall. This metric is generated only when there is active I/O (such as file reads or recalls) on the server endpoint.| Storage Sync Service - Metrics |
104
104
| Cloud tiering size of data tiered | Size of data tiered | Storage Sync Service - Metrics |
105
105
| Cloud tiering size of data tiered by last maintenance job | Size of data tiered during last maintenance job. | Storage Sync Service - Metrics |
106
106
| Cloud tiering recall size | Size of data recalled | Sync Group – Status, Registered Servers, Storage Sync Service - Metrics |
107
-
| Cloud tiering recall size by application | Size of data recalled by application | Server Endpoint - Cloud Tiering Status, Storage Sync Service - Metrics |
108
-
| Cloud tiering recall throughput | Throughput of data recalled | Storage Sync Service - Metrics |
107
+
| Cloud tiering recall size by application | Size of data recalled by application. This metric is generated only when there is active I/O (such as file reads or recalls) on the server endpoint.| Server Endpoint - Cloud Tiering Status, Storage Sync Service - Metrics |
108
+
| Cloud tiering recall throughput | Throughput of data recalled. This metric is generated only when there is active I/O (such as file reads or recalls) on the server endpoint.| Storage Sync Service - Metrics |
109
109
| Egress Breakdown | Egress breakdown by user recalls of tiered files, background recalls, and sync downloads | Server Endpoint - Cloud Tiering Status |
110
110
| Files synced | Count of files transferred (upload and download) | Sync Group - Status, Server endpoint - Sync status, Storage Sync Service - Metrics |
111
111
| Files not syncing | Count of files that are failing to sync | Sync Group - Status, Server endpoint - Sync status, Storage Sync Service - Metrics |
![learn-build-service-prod[bot]](https://avatars.githubusercontent.com/in/237442?v=4&size=40){kind=avatar}
0 commit comments