From 063b7157d466c19206274b2dfc73b678807984b1 Mon Sep 17 00:00:00 2001 From: Takashi Takebayashi Date: Sat, 18 Oct 2025 22:33:49 +0900 Subject: [PATCH] Fix typo: Seemless -> Seamless --- articles/operator-service-manager/release-notes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/articles/operator-service-manager/release-notes.md b/articles/operator-service-manager/release-notes.md index 317457a8474f7..2bb80bed36272 100644 --- a/articles/operator-service-manager/release-notes.md +++ b/articles/operator-service-manager/release-notes.md @@ -47,7 +47,7 @@ Azure Operator Service Manager is a cloud orchestration service that enables aut **[FEATURE 2069409 / ART-465]** introduces a method to interrupt a broken service deployment operation while in a nonterminal state. Supporting only container network functions, the interruption is triggered by applying a static tag to the network function managed resource group. This tag must later be removed to restore proper service operations. This feature provides a mechanism for customer operation teams to terminate a deployment which maybe negatively impacting service performance and otherwise could take multiple hours to reach a terminal state. For more information, see our [learn documentation](how-to-cancel-service-deployments.md). #### Support for publisher artifact store resiliency -**[FEATURE 2129209 / ART-535]** introduces artifact store geo-resiliency between the backing ACR resources in two Azure regional location pairs. Once enabled, the artifact-store resource now survives a single region failure, continuing to operate in read-only mode from the hot standby instance. Seemless integration with Azure Operator Service Manager's cluster registry, combined with centralized management of registry pairs, make artifact store resiliency to get and keep running. For more information, see our [learn documentation](publisher-artifact-store-resiliency.md). +**[FEATURE 2129209 / ART-535]** introduces artifact store geo-resiliency between the backing ACR resources in two Azure regional location pairs. Once enabled, the artifact-store resource now survives a single region failure, continuing to operate in read-only mode from the hot standby instance. Seamless integration with Azure Operator Service Manager's cluster registry, combined with centralized management of registry pairs, make artifact store resiliency to get and keep running. For more information, see our [learn documentation](publisher-artifact-store-resiliency.md). ### Latest release updates to improve quality The following bug fixes, defect resolutions, or usability improvements are delivered with this release, for either Network Function Operator (NFO) or resource provider (RP) components.