Skip to content

Commit 137b0c8

Browse files
Merge pull request #307225 from MicrosoftDocs/main
Auto Publish – main to live - 2025-10-22 11:00 UTC
2 parents 63d2083 + e30c2de commit 137b0c8

File tree

13 files changed

+40
-40
lines changed

13 files changed

+40
-40
lines changed

articles/azure-maps/release-notes-map-control.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ titleSuffix: Microsoft Azure Maps
44
description: Release notes for the Azure Maps Web SDK.
55
author: sinnypan
66
ms.author: sipa
7-
ms.date: 10/20/2025
7+
ms.date: 10/22/2025
88
ms.topic: reference
99
ms.service: azure-maps
1010
ms.subservice: web-sdk
@@ -16,7 +16,7 @@ This document contains information about new features and other changes to the M
1616

1717
## v3 (latest)
1818

19-
### [3.7.1] (CDN: October 20, 2025, npm: TBA)
19+
### [3.7.1] (CDN: October 20, 2025, npm: October 22, 2025)
2020

2121
#### New features
2222
- Add support for zoom level 0, allowing users to view the entire globe within a small map canvas.
@@ -654,6 +654,7 @@ Stay up to date on Azure Maps:
654654
> [!div class="nextstepaction"]
655655
> [Azure Maps Blog]
656656

657+
[3.7.1]: https://www.npmjs.com/package/azure-maps-control/v/3.7.1
657658
[3.6.1]: https://www.npmjs.com/package/azure-maps-control/v/3.6.1
658659
[3.6.0]: https://www.npmjs.com/package/azure-maps-control/v/3.6.0
659660
[3.5.0]: https://www.npmjs.com/package/azure-maps-control/v/3.5.0

articles/azure-netapp-files/migrate-volumes.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: azure-netapp-files
55
author: b-ahibbard
66
ms.service: azure-netapp-files
77
ms.topic: how-to
8-
ms.date: 09/09/2025
8+
ms.date: 10/22/2025
99
ms.author: anfdocs
1010
---
1111
# Migrate volumes to Azure NetApp Files
@@ -74,7 +74,7 @@ The network connectivity must be in place for all intercluster (IC) LIFs on the
7474
>[!IMPORTANT]
7575
>Ensure the size and other volume properties on the target volumes match with the source.
7676
>
77-
>You should create the Azure NetApp Files volume with 20% or more quota than the source volume. Azure NetApp Files volumes use raw capacity size. The source volume might be smaller due to deduplication and compression. You can shrink Azure NetApp Files nondisruptively after the migration to prevent over-provisioning.
77+
>You should create the Azure NetApp Files volume with 20% or more quota than the source volume. Azure NetApp Files volumes use logical capacity size. The source volume might be smaller due to deduplication and compression. For correct Azure NetApp Files volume sizing, use the logical space reported by the volume you are migrating. You can shrink Azure NetApp Files nondisruptively after the migration to prevent over-provisioning.
7878
7979
The "remote path" values are the host, server, and volume names of your on-premises storage.
8080

articles/backup/backup-support-matrix-mars-agent.md

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Support matrix for the MARS agent
33
description: This article summarizes Azure Backup support when you back up machines that are running the Microsoft Azure Recovery Services (MARS) agent.
4-
ms.date: 08/21/2025
4+
ms.date: 10/22/2025
55
ms.topic: reference
66
ms.custom: engagement-fy24
77
author: AbhishekMallick-MS
@@ -70,11 +70,11 @@ Windows 10 (Enterprise, Pro, Home, IoT Enterprise) | Yes | No | Check the corre
7070
Windows 8.1 (Enterprise, Pro)| Yes |No | Check the corresponding server version for software/module requirements
7171
Windows 8 (Enterprise, Pro) | Yes | No | Check the corresponding server version for software/module requirements
7272
Windows Server 2022 (Standard, Datacenter, Essentials, Server IoT) | Yes | Yes | Check the corresponding server version for software/module requirements
73-
Windows Server 2019 (Standard, Datacenter, Essentials, Server IoT) | Yes | Yes | - .NET 4.5 <br> - Windows PowerShell <br> - Latest Compatible Microsoft VC++ Redistributable <br> - Microsoft Management Console (MMC) 3.0
74-
Windows Server 2016 (Standard, Datacenter, Essentials) | Yes | Yes | - .NET 4.5 <br> - Windows PowerShell <br> - Latest Compatible Microsoft VC++ Redistributable <br> - Microsoft Management Console (MMC) 3.0
75-
Windows Storage Server 2016/2012 R2/2012 (Standard, Workgroup) | Yes | No | - .NET 4.5 <br> - Windows PowerShell <br> - Latest Compatible Microsoft VC++ Redistributable <br> - Microsoft Management Console (MMC) 3.0
76-
Windows Server 2012 R2 (Standard, Datacenter, Foundation, Essentials) | Yes | Yes | - .NET 4.5 <br> - Windows PowerShell <br> - Latest Compatible Microsoft VC++ Redistributable <br> - Microsoft Management Console (MMC) 3.0
77-
Windows Server 2012 (Standard, Datacenter, Foundation) | Yes | Yes |- .NET 4.5 <br> -Windows PowerShell <br> - Latest Compatible Microsoft VC++ Redistributable <br> - Microsoft Management Console (MMC) 3.0 <br> - Deployment Image Servicing and Management (DISM.exe)
73+
Windows Server 2019 (Standard, Datacenter, Essentials, Server IoT) | Yes | Yes | - .NET 4.8 <br> - Windows PowerShell <br> - Latest Compatible Microsoft VC++ Redistributable <br> - Microsoft Management Console (MMC) 3.0
74+
Windows Server 2016 (Standard, Datacenter, Essentials) | Yes | Yes | - .NET 4.8 <br> - Windows PowerShell <br> - Latest Compatible Microsoft VC++ Redistributable <br> - Microsoft Management Console (MMC) 3.0
75+
Windows Storage Server 2016/2012 R2/2012 (Standard, Workgroup) | Yes | No | - .NET 4.8 <br> - Windows PowerShell <br> - Latest Compatible Microsoft VC++ Redistributable <br> - Microsoft Management Console (MMC) 3.0
76+
Windows Server 2012 R2 (Standard, Datacenter, Foundation, Essentials) | Yes | Yes | - .NET 4.8 <br> - Windows PowerShell <br> - Latest Compatible Microsoft VC++ Redistributable <br> - Microsoft Management Console (MMC) 3.0
77+
Windows Server 2012 (Standard, Datacenter, Foundation) | Yes | Yes |- .NET 4.8 <br> -Windows PowerShell <br> - Latest Compatible Microsoft VC++ Redistributable <br> - Microsoft Management Console (MMC) 3.0 <br> - Deployment Image Servicing and Management (DISM.exe)
7878

7979

8080
For more information, see [Supported MABS and DPM operating systems](backup-support-matrix-mabs-dpm.md#supported-mabs-and-dpm-operating-systems).
@@ -187,6 +187,7 @@ The following table lists the previous versions of the agent with their download
187187
[2.0.9197.0](https://download.microsoft.com/download/2/7/5/27531ace-3100-43bc-b4af-7367680ea66b/MARSAgentInstaller.exe) | [4589598](https://support.microsoft.com/help/4589598)
188188
[2.0.9207.0](https://download.microsoft.com/download/b/5/a/b5a29638-1cef-4906-b704-4d3d914af76e/MARSAgentInstaller.exe) | [5001305](https://support.microsoft.com/help/5001305)
189189
[2.0.9415.0](https://download.microsoft.com/download/MARSAgentInstaller.exe) |[5059322](https://support.microsoft.com/help/5059322)
190+
[2.0.9506.0](https://download.microsoft.com/download/398f1a94-03fb-4de2-af98-dbe8ff925f49/MARSAgentInstaller.exe) | [5068415](https://support.microsoft.com/help/5068415)
190191

191192
>[!NOTE]
192193
>MARS agent versions with minor reliability and performance improvements don't have a KB article.

articles/backup/install-mars-agent.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -128,6 +128,12 @@ To install and register the MARRS agent, follow these steps:
128128
![Screenshot shows how to set up internet access in the MARS wizard.](./media/backup-configure-vault/mars2.png)
129129

130130
1. For **Installation**, review the prerequisites, and select **Install**.
131+
132+
>[!Note]
133+
>MARS agent installation requires Windows Powershell 5.0 and Microsoft .NET Framework 4.8 (previously 4.5). You might need to install the .NET Framework 4.8 manually when upgrading from version 4.5.
134+
135+
![Screenshot shows the prerequisites required to configure MARS agent.](./media/backup-configure-vault/mars-prerequisite.png)
136+
131137
1. After the agent is installed, select **Proceed to Registration**.
132138
1. In **Register Server Wizard** > **Vault Identification**, browse to and select the credentials file that you downloaded. Then select **Next**.
133139

139 KB
Loading

articles/migrate/toc.yml

Lines changed: 6 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -37,8 +37,6 @@ items:
3737
href: concepts-vmware-agentless-migration.md
3838
- name: Hyper-V migration architecture
3939
href: hyper-v-migration-architecture.md
40-
- name: VMware to Azure disaster recovery hyper-v-migration-architecture.md
41-
href: ../site-recovery/vmware-azure-architecture-modernized.md?toc=/azure/migrate/toc.json
4240
- name: Discover inventory
4341
items:
4442
- name: Discovery methods
@@ -209,6 +207,10 @@ items:
209207
items:
210208
- name: Overview of migration method
211209
href: server-migrate-overview.md
210+
- name: Agentless migrations using portal
211+
href: tutorial-migrate-vmware.md
212+
- name: Agent-based migration using portal
213+
href: tutorial-migrate-vmware-agent.md
212214
- name: Support Matrix
213215
items:
214216
- name: VMware vSphere migration requirements
@@ -219,14 +221,8 @@ items:
219221
href: migrate-support-matrix-hyper-v-migration.md
220222
# - name: Agent-based migrations
221223
# items:
222-
# - name: Agent-based migration using portal
223-
# href: tutorial-migrate-vmware-agent.md
224224
# - name: Hydration process
225225
# href: hydration-process.md
226-
# - name: Agentless migrations
227-
# items:
228-
# - name: Agentless migrations using portal
229-
# href: tutorial-migrate-vmware.md
230226
# - name: Agentless migrations using scripts
231227
# href: tutorial-migrate-vmware-powershell.md
232228
# - name: Limitations
@@ -252,8 +248,8 @@ items:
252248
items:
253249
- name: Migrate VMware servers
254250
items:
255-
- name: Assess VMWare servers
256-
href: ../azure-vmware/tutorial-access-private-cloud.md?toc=/azure/migrate/toc.json&bc=/azure/migrate/breadcrumb/toc.json
251+
- name: Assess VMware servers
252+
href: tutorial-assess-vmware-azure-vm.md
257253
- name: Migrate to Azure Cloud
258254
href: tutorial-migrate-vmware.md
259255
- name: Migrate to Azure Local

articles/sentinel/indicators-bulk-file-import.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,8 +23,6 @@ ms.custom: sfi-image-nochange
2323
This article demonstrates how to add indicators from a CSV or STIX objects from a JSON file into Microsoft Sentinel threat intelligence. Because threat intelligence sharing still happens across emails and other informal channels during an ongoing investigation, the ability to import that information quickly into Microsoft Sentinel is important to relay emerging threats to your team. These identified threats are then available to power other analytics, such as producing security alerts, incidents, and automated responses.
2424

2525
> [!IMPORTANT]
26-
> This feature is currently in preview. See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for more legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
27-
>
2826
> [!INCLUDE [unified-soc-preview-without-alert](includes/unified-soc-preview-without-alert.md)]
2927
3028
## Prerequisites
11 KB
Loading

articles/sentinel/search-jobs.md

Lines changed: 6 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -46,27 +46,23 @@ Go to **Search** in Microsoft Sentinel from the Azure portal or the Microsoft De
4646
:::image type="content" source="media/search-jobs/search-job-criteria.png" alt-text="Screenshot of search page with search criteria of administrator, time range last 90 days, and table selected." lightbox="media/search-jobs/search-job-criteria.png":::
4747
---
4848

49-
1. Select the **Start** to open the advanced Kusto Query Language (KQL) editor and preview of the results for a set time range.
49+
1. Select the **Start** to preview your results for a set time range in **Simple Mode**. If needed, go to the dropdown menu and switch from **Simple mode** to **KQL mode** to open the advanced Kusto Query Language (KQL) editor.
5050

51-
1. Change the KQL query as needed and select **Run** to get an updated preview of the search results.
51+
1. Change the KQL query as needed and select **Run** to get an updated preview of the search results. Resolve any KQL issues indicated by a squiggly red line in the editor.
5252

5353
:::image type="content" source="media/search-jobs/search-job-advanced-kql-edit.png" alt-text="Screenshot of KQL editor with revised search.":::
5454

55-
1. When you're satisfied with the query and the search results preview, select the ellipses **...** and toggle **Search job mode** on.
55+
1. When you're satisfied with the query and the search results preview, select the ellipses **...** and select **Search job** to open the **Search Job Mode** window.
5656

57-
:::image type="content" source="media/search-jobs/search-job-advanced-kql-ellipsis.png" alt-text="Screenshot of KQL editor with revised search with ellipsis highlighted for Search job mode." lightbox="media/search-jobs/search-job-advanced-kql-ellipsis.png":::
57+
:::image type="content" source="media/search-jobs/search-job-advanced-kql-ellipsis.png" alt-text="Screenshot of KQL editor with revised search with ellipsis highlighted in order to select Search job, which will open the Search Job Mode window." lightbox="media/search-jobs/search-job-advanced-kql-ellipsis.png":::
5858

5959
1. Specify the search job date range using the **Time range** selector. If your query also specifies a time range, Microsoft Sentinel runs the search job on the union of the time ranges.
6060

61-
1. Resolve any KQL issues indicated by a squiggly red line in the editor.
62-
63-
1. When you're ready to start the search job, select **Search job**.
64-
6561
1. Enter a new table name to store the search job results.
6662

67-
1. Select **Run a search job**.
63+
1. Select **Run search job**.
6864

69-
1. Wait for the notification **Search job is done** to view the results.
65+
1. Wait for the notification **Search job is done** and select the button to go to the table and view the results.
7066

7167
## View search job results
7268

articles/site-recovery/azure-to-azure-how-to-reprotect.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,12 @@
11
---
22
title: Reprotect Azure virtual machines to the primary region with Azure Site Recovery
3+
ms.reviewer: v-gajeronika
34
description: Describes how to reprotect Azure virtual machines after failover, the secondary to primary region, using Azure Site Recovery.
45
services: site-recovery
56
author: Jeronika-MS
67
ms.service: azure-site-recovery
78
ms.topic: tutorial
8-
ms.date: 08/29/2025
9+
ms.date: 10/22/2025
910
ms.author: v-gajeronika
1011
# Customer intent: As an IT administrator managing disaster recovery for virtual machines, I want to reprotect VMs to the primary region after a failover, so that I can ensure continuous data replication and quickly restore services to their original location.
1112
---
@@ -26,12 +27,12 @@ When you [fail over](site-recovery-failover.md) Azure virtual machines from one
2627

2728
1. In **Vault** > **Replicated items**, right-click the failed over virtual machine, and select **Re-Protect**. The reprotection direction should show from secondary to primary.
2829

29-
:::image type="content" source="./media/site-recovery-how-to-reprotect-azure-to-azure/reprotect.png" alt-text="Screenshot shows a virtual machine with a contextual menu with Re-protect selected." lightbox="./media/site-recovery-how-to-reprotect-azure-to-azure/reprotect.png":::
30+
:::image type="content" source="./media/site-recovery-how-to-reprotect-azure-to-azure/reprotect-failedover-virtual-machine.png" alt-text="Screenshot shows a virtual machine with a contextual menu with Re-protect selected." lightbox="./media/site-recovery-how-to-reprotect-azure-to-azure/reprotect-failedover-virtual-machine.png":::
3031

3132
1. Review the resource group, network, storage, and availability sets. Then select **OK**. If there are any resources marked as new, they're created as part of the reprotection process.
3233
1. The reprotection job seeds the target site with the latest data. After the job finishes, delta replication takes place. Then, you can fail over back to the primary site. You can select the storage account or the network you want to use during reprotect, using the customize option.
3334

34-
:::image type="content" source="./media/site-recovery-how-to-reprotect-azure-to-azure/customize.png" alt-text="Screenshot displays Customize option on the Azure portal." lightbox="./media/site-recovery-how-to-reprotect-azure-to-azure/customize.png":::
35+
:::image type="content" source="./media/site-recovery-how-to-reprotect-azure-to-azure/customize-settings.png" alt-text="Screenshot displays Customize option on the Azure portal." lightbox="./media/site-recovery-how-to-reprotect-azure-to-azure/customize-settings.png":::
3536

3637
### Customize reprotect settings
3738

@@ -114,4 +115,4 @@ The above is a simple illustration of how to estimate the reprotection time. Whe
114115

115116
After the virtual machine is protected, you can initiate a failover. The failover shuts down the virtual machine in the secondary region and creates and boots the virtual machine in the primary region, with brief downtime during this process. We recommend you choose an appropriate time for this process and that you run a test failover before initiating a full failover to the primary site.
116117

117-
[Learn more](site-recovery-failover.md) about Azure Site Recovery failover.
118+
[Learn more](site-recovery-failover.md) about Azure Site Recovery failover.

0 commit comments

Comments
 (0)