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
Copy file name to clipboardExpand all lines: articles/backup/backup-azure-immutable-vault-how-to-manage.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
@@ -100,7 +100,7 @@ However, increasing the retention of backup items that are in suspended state is
100
100
Let's try to stop backup on a VM and choose **Retain as per policy** for backup data retention.
101
101
102
102
>[!NOTE]
103
-
> When you stop backups and retain as per policy, the last RP is retained forever to ensure recovery against any unforeseen ransomware scenarios. You must manually delete this RP after the backup policy expires to stop incurring PI charges.
103
+
> When you stop backups and retain as per policy, the last RPs (one in snapshot tier and one in vault tier) are retained forever to ensure recovery against any unforeseen ransomware scenarios. You must manually delete these RPs after the backup policy expires to stop incurring PI charges.
104
104
105
105
:::image type="content" source="./media/backup-azure-immutable-vault/attempt-to-increase-retention-of-backup-items-in-suspended-state.png" alt-text="Screenshot shows an attempt to increase retention of backup items in suspended state.":::
Copy file name to clipboardExpand all lines: articles/cloud-services-extended-support/cloud-services-guestos-update-matrix.md
+15-9Lines changed: 15 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,13 +3,13 @@ title: Learn about the latest Azure Guest OS Releases | Microsoft Docs
3
3
description: The latest release news and SDK compatibility for Azure Cloud Services Guest OS.
4
4
services: cloud-services
5
5
ms.subservice: guest-os-patching
6
-
author: jejackson
6
+
author: aschoksh
7
7
ms.assetid: 6306cafe-1153-44c7-8554-623b03d59a34
8
8
ms.service: azure-cloud-services-classic
9
9
ms.topic: concept-article
10
-
ms.date: 09/08/2025
10
+
ms.date: 10/06/2025
11
11
ms.update-cycle: 3650-days
12
-
ms.author: acastoldi
12
+
ms.author: aschoksh
13
13
ms.custom: compute-evergreen
14
14
# Customer intent: As a cloud services administrator, I want to stay updated on the latest Guest OS releases and their compatibility, so that I can plan timely upgrades and ensure my applications remain secure and functional before any deprecation deadlines.
15
15
---
@@ -40,6 +40,9 @@ Unsure about how to update your Guest OS? Check [this][cloud updates] out.
40
40
41
41
## News updates
42
42
43
+
###### **October 6, 2025**
44
+
The September 2025 Guest OS released.
45
+
43
46
###### **September 6, 2025**
44
47
The August 2025 Guest OS released.
45
48
@@ -301,9 +304,10 @@ The September Guest OS released.
301
304
302
305
| Configuration string | Release date | Disable date |
303
306
| --- | --- | --- |
307
+
| WA-GUEST-OS-7.56_202509-01 | October 6, 2025 | Post 7.59 |
304
308
| WA-GUEST-OS-7.55_202508-01 | September 6, 2025 | Post 7.58 |
305
309
| WA-GUEST-OS-7.54_202507-01 | July 30, 2025 | Post 7.57 |
306
-
|WA-GUEST-OS-7.53_202506-01| July 6, 2025 | Post 7.56 |
310
+
|~~WA-GUEST-OS-7.53_202506-01~~| July 6, 2025 | Post 7.56 |
307
311
|~~WA-GUEST-OS-7.52_202505-01~~| June 4, 2025 | Post 7.55 |
308
312
|~~WA-GUEST-OS-7.51_202504-01~~| May 1, 2025 | July 30, 2025 |
309
313
|~~WA-GUEST-OS-7.50_202503-01~~| March 28, 2025 | July 6, 2025 |
@@ -361,9 +365,10 @@ The September Guest OS released.
361
365
362
366
| Configuration string | Release date | Disable date |
363
367
| --- | --- | --- |
368
+
| WA-GUEST-OS-6.86_202509-01 | October 6, 2025 | Post 6.89 |
364
369
| WA-GUEST-OS-6.85_202508-01 | September 6, 2025 | Post 6.88 |
365
370
| WA-GUEST-OS-6.84_202507-01 | July 30, 2025 | Post 6.87 |
366
-
|WA-GUEST-OS-6.83_202506-01| July 6, 2025 | Post 6.86 |
371
+
|~~WA-GUEST-OS-6.83_202506-01~~| July 6, 2025 | Post 6.86 |
367
372
|~~WA-GUEST-OS-6.82_202505-01~~| June 4, 2025 | Post 6.85 |
368
373
|~~WA-GUEST-OS-6.81_202504-01~~| May 1, 2025 | July 30, 2025 |
369
374
|~~WA-GUEST-OS-6.80_202503-01~~| March 28, 2025 | July 6, 2025 |
@@ -455,10 +460,11 @@ The September Guest OS released.
455
460
456
461
| Configuration string | Release date | Disable date |
457
462
| --- | --- | --- |
458
-
| WA-GUEST-OS-5.109_202508-01 | September 6, 2025 | Post 5.111 |
459
-
| WA-GUEST-OS-5.108_202507-01 | July 30, 2025 | Post 5.110 |
460
-
| WA-GUEST-OS-5.107_202506-01 | July 6, 2025 | Post 5.109 |
461
-
|~~WA-GUEST-OS-5.106_202505-01~~| June 4, 2025 | Post 5.108 |
463
+
| WA-GUEST-OS-5.110_202509-01 | October 6, 2025 | Post 5.113 |
464
+
| WA-GUEST-OS-5.109_202508-01 | September 6, 2025 | Post 5.112 |
465
+
| WA-GUEST-OS-5.108_202507-01 | July 30, 2025 | Post 5.111 |
466
+
|~~WA-GUEST-OS-5.107_202506-01~~| July 6, 2025 | Post 5.110 |
467
+
|~~WA-GUEST-OS-5.106_202505-01~~| June 4, 2025 | Post 5.109 |
462
468
|~~WA-GUEST-OS-5.105_202504-01~~| May 1, 2025 | July 30, 2025 |
463
469
|~~WA-GUEST-OS-5.104_202503-01~~| March 28, 2025 | July 6, 2025 |
464
470
|~~WA-GUEST-OS-5.103_202502-01~~| February 26, 2025 | June 4, 2025 |
Copy file name to clipboardExpand all lines: articles/expressroute/gateway-migration.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -64,6 +64,7 @@ The guided gateway migration experience has the following limitations:
64
64
-**Private Endpoint Connectivity**: Private endpoints (PEs) connected via ExpressRoute private peering may experience **connectivity issues** during migration. Refer to guidance on mitigating these issues in the Private endpoint connectivity documentation. [Private endpoint connectivity](expressroute-about-virtual-network-gateways.md#private-endpoint-connectivity-and-planned-maintenance-events).
65
65
-**Legacy Gateways**: ExpressRoute gateways created or connected to circuits in **2017 or earlier** aren't supported.
66
66
-**Unsupported SKUs**: Gateways using the **"default" SKU** aren't eligible for migration. To check the migration eligibility of your Gateway, there should be an Advisor notification.
67
+
-**Incompatible dedicated circuit**: Gateway migration can't proceed with a dedicated Hardware Security Module (HSM) connected to the virtual network. To proceed with the migration, deallocate the dedicated Hardware Security Module (HSM). For detailed troubleshooting steps, see [Troubleshoot Dedicated HSM](/azure/dedicated-hsm/troubleshoot).
67
68
68
69
For detailed troubleshooting errors and best practices, see [Troubleshooting Gateway Migration](gateway-migration-error-messaging.md).
Copy file name to clipboardExpand all lines: articles/firmware-analysis/tutorial-analyze-firmware.md
+2-5Lines changed: 2 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,13 +15,10 @@ This tutorial describes how to use the **firmware analysis** page to upload a fi
15
15
16
16
## Prerequisites
17
17
18
-
> [!NOTE]
19
-
> The **firmware analysis** feature is automatically available if you currently access Defender for IoT using the Security Admin, Contributor, or Owner role. If you only have the Security Reader role or want to use **firmware analysis** as a standalone feature, then your Admin must give the Firmware Analysis Admin role. For additional information, please see [Firmware analysis Azure RBAC](./firmware-analysis-rbac.md).
20
-
>
21
-
22
18
* If you don't have an Azure subscription, [create a free account](https://azure.microsoft.com/free/) before you begin.
23
19
* If you have a subscription but don't have a resource group where you could upload your firmware images, [create a resource group](/azure/azure-resource-manager/management/manage-resource-groups-portal#create-resource-groups).
24
-
* If you already have a subscription and resource group, move on to the next section.
20
+
* Make sure you have Security Admin, Contributor, or Owner role in your resource group. If you only have the Security Reader role or want to use **firmware analysis** as a standalone feature, then your Admin must give the Firmware Analysis Admin role. For additional information, please see [Firmware analysis Azure RBAC](./firmware-analysis-rbac.md).
21
+
* If you already have a subscription and resource group, and have the proper permissions, move on to the next section.
25
22
26
23
To use the **firmware analysis** page to analyze your firmware security, your firmware image must have the following prerequisites:
Copy file name to clipboardExpand all lines: articles/iot-operations/includes/supported-versions.md
+8-13Lines changed: 8 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,30 +3,25 @@ title: Include file
3
3
description: Include file with details of currently supported versions
4
4
author: dominicbetts
5
5
ms.topic: include
6
-
ms.date: 09/29/2025
6
+
ms.date: 10/06/2025
7
7
ms.author: dobett
8
8
---
9
9
10
-
Microsoft supports three generally available (GA) versions of Azure IoT Operations at any time: the latest version, and the two previous minor versions.
10
+
Microsoft supports three generally available (GA) versions of Azure IoT Operations at any time: the latest version, and the two previous minor versions. Additionally, preview versions are available for testing new features.
11
11
12
-
Currently, there are two supported minor GA versions. [Azure support](https://azure.microsoft.com/support/plans) is available for the following GA versions:
12
+
Currently, [Azure support](https://azure.microsoft.com/support/plans) is available for the following versions:
13
13
14
-
| Version | Patch release (YYMM) | CLI version | Release notes |
| 1.1.x | GA | 1.1.59 (2506) |[1.7.0](https://github.com/Azure/azure-iot-ops-cli-extension/releases/tag/v1.7.0)|[Release notes](https://github.com/Azure/azure-iot-operations/releases/tag/v1.1.59)|
18
+
| 1.0.x | GA | 1.0.34 (2503) |[1.3.0](https://github.com/Azure/azure-iot-ops-cli-extension/releases/tag/v1.3.0)|[Release notes](https://github.com/Azure/azure-iot-operations/releases/tag/v1.0.34)|
18
19
19
20
To learn about upgrades between versions, see [Upgrade to a new version](../deploy-iot-ops/howto-upgrade.md).
20
21
21
22
> [!IMPORTANT]
22
23
> Previous minor versions don't receive security patches. Upgrade to the latest version to get the latest security updates and features.
23
24
24
-
Currently, there's only one supported preview version. [Azure support](https://azure.microsoft.com/support/plans) is available for the following preview version:
25
-
26
-
| Version | Patch release (YYMM) | CLI version | Release notes |
Copy file name to clipboardExpand all lines: articles/operator-service-manager/release-notes.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
@@ -476,10 +476,10 @@ The following bug fixes, defect resolutions, or usability improvements are deliv
476
476
Document Revision 2.0
477
477
478
478
### Release Summary
479
-
Azure Operator Service Manager is a cloud orchestration service that enables automation of operator network-intensive workloads, and mission critical applications hosted on Azure Operator Nexus. Azure Operator Service Manager unifies infrastructure, software, and configuration management with a common model into a single interface, both based on trusted Azure industry standards. This 2509.01 Azure Operator Service Manager release includes updating the NFO version to 3.0.3194.224 and the RP version to 1.0.03180.486, the details of which are further outlined in the remainder of this document.
479
+
Azure Operator Service Manager is a cloud orchestration service that enables automation of operator network-intensive workloads, and mission critical applications hosted on Azure Operator Nexus. Azure Operator Service Manager unifies infrastructure, software, and configuration management with a common model into a single interface, both based on trusted Azure industry standards. This 2509.01 Azure Operator Service Manager release includes updating the NFO version to 3.0.3194-224 and the RP version to 1.0.03180.486, the details of which are further outlined in the remainder of this document.
480
480
481
481
### Release Details
482
-
* Release Version: NFO version 3.0.3194.224, RP version 1.0.03180.486
482
+
* Release Version: NFO version 3.0.3194-224, RP version 1.0.03180.486
483
483
* Release Date: September 30, 2025
484
484
* Is NFO update required: YES, Update only
485
485
* Dependency Versions: Go/1.24.3 - Helm/3.18.4 - Base Image/AzureLinux 3.0
> | Microsoft.Communication/CommunicationServices/SmtpUsernames/read | Get an SMTP username resource. |
695
694
> | Microsoft.Communication/CommunicationServices/SmtpUsernames/write | Add SMTP username resource or update an existing resource. |
696
695
> | Microsoft.Communication/CommunicationServices/SmtpUsernames/delete | Operation to delete an SMTP username resource. |
@@ -699,7 +698,6 @@ Azure service: [Azure Communication Services](/azure/communication-services/over
699
698
> | Microsoft.Communication/CommunicationServicesGccm/Delete | Deletes communication services |
700
699
> | Microsoft.Communication/CommunicationServicesGccm/ListKeys/action | Reads the keys for a communication service |
701
700
> | Microsoft.Communication/CommunicationServicesGccm/RegenerateKey/action | Regenerates the primary or secondary key for a communication service |
702
-
> | Microsoft.Communication/CommunicationServicesGccm/LinkNotificationHub/action | Links an Azure Notification Hub to the communication service |
703
701
> | Microsoft.Communication/CommunicationServicesGccm/EventGridFilters/Read | Reads EventGrid filters on communication services |
704
702
> | Microsoft.Communication/CommunicationServicesGccm/EventGridFilters/Write | Writes EventGrid filters on communication services |
705
703
> | Microsoft.Communication/CommunicationServicesGccm/EventGridFilters/Delete | Removes an EventGrid filter on communication services |
@@ -711,8 +709,6 @@ Azure service: [Azure Communication Services](/azure/communication-services/over
711
709
> | Microsoft.Communication/EmailServices/Domains/write | Add a new Domain under the parent EmailService resource or update an existing Domain resource. |
712
710
> | Microsoft.Communication/EmailServices/Domains/delete | Operation to delete a Domain resource. |
713
711
> | Microsoft.Communication/EmailServices/Domains/InitiateVerification/action | Initiate verification of Dns record. |
714
-
> | Microsoft.Communication/EmailServices/Domains/CancelVerification/action | Cancel verification of Dns record. |
715
-
> | Microsoft.Communication/EmailServices/Domains/RevokeVerification/action | Revoke existing verified status of a Dns record. |
716
712
> | Microsoft.Communication/EmailServices/Domains/SenderUsernames/read | List all valid sender usernames for a domains resource. |
717
713
> | Microsoft.Communication/EmailServices/Domains/SenderUsernames/read | Get the email SenderUsername and its properties. |
718
714
> | Microsoft.Communication/EmailServices/Domains/SenderUsernames/write | Add a new SenderUsername under the parent Domain resource or update an existing SenderUsername resource. |
@@ -725,11 +721,9 @@ Azure service: [Azure Communication Services](/azure/communication-services/over
725
721
> | Microsoft.Communication/EmailServices/Domains/SuppressionLists/SuppressionListAddresses/read | Get all the addresses in a suppression list. |
726
722
> | Microsoft.Communication/EmailServices/Domains/SuppressionLists/SuppressionListAddresses/write | Add a new suppression list under the parent Domain resource or update an existing suppression list. |
727
723
> | Microsoft.Communication/EmailServices/Domains/SuppressionLists/SuppressionListAddresses/delete | Operation to delete an address from a suppression list. |
728
-
> | Microsoft.Communication/locations/notifyNetworkSecurityPerimeterUpdatesAvailable/action | Notifies that new Network Security Perimeter updates are available |
729
724
> | Microsoft.Communication/Locations/OperationStatuses/read | Reads the status of an async operation |
730
725
> | Microsoft.Communication/Locations/OperationStatuses/write | Writes the status of an async operation |
731
726
> | Microsoft.Communication/Locations/Usages/Read | Get email quota for the subscription |
![learn-build-service-prod[bot]](https://avatars.githubusercontent.com/in/237442?v=4&size=40){kind=avatar}
0 commit comments