Merge pull request #311987 from MicrosoftDocs/main

Auto Publish – main to live - 2026-02-19 06:00 UTC

Author: learn-build-service-prod[bot]

articles/communication-services/concepts/government.md

@@ -6,28 +6,26 @@ author: hrazi
 manager: mharbut
 services: azure-communication-services
 
-ms.date: 03/09/2023
+ms.date: 02/18/2026
 ms.author: harazi
 ms.topic: conceptual 
 ms.service: azure-communication-services
 ---
 
 # Azure Communication Services for US Government
 
-[!INCLUDE [Public Preview Notice](../includes/public-preview-include.md)]
-
 You can use Azure Communication Services within [Azure Government](https://azure.microsoft.com/global-infrastructure/government/) to provide compliance with US government requirements for cloud services. In addition to enjoying the features and capabilities of Messaging, Voice and Video calling, developers benefit from the following features that are unique to Azure Government:
 - Your personal data is logically segregated from customer content in the commercial Azure cloud.
 - Your resource’s customer content is stored within the United States.
 - Access to your organization's customer content is restricted to screened Microsoft personnel. 
 
-Azure Communication Services in Azure Government is currently In Process for the FedRAMP High accreditation as part of the [Microsoft 365 Government Community Cloud (GCC) - High service offering](https://marketplace.fedramp.gov/products/FR1824057433). Once the FedRAMP High certification process is completed and the authorization is granted, Azure Communication Services in the Azure Government cloud moves to GA. Then the government services officially meet the requirements of FedRAMP. Government customers can then use the service that is secure and compliant with federal standards.
+Azure Communication Services in Azure Government has achieved FedRAMP High accreditation as part of the [Microsoft 365 Government Community Cloud (GCC) - High service offering](https://marketplace.fedramp.gov/products/FR1824057433). The service is now Generally Available (GA) and meets the requirements of FedRAMP. Government customers can use the service knowing it is secure and compliant with federal standards.
 
 ## General availability and feature releases
 
-Azure Communication Services for US Government is scheduled for General Availability (GA) in 2025. The initial release focuses on delivering core capabilities, including basic video calling and messaging, to provide government customers with a secure and compliant communication solution.
+Azure Communication Services for US Government is now Generally Available (GA). The initial release delivers core capabilities, including basic video calling and messaging, to provide government customers with a secure and compliant communication solution.
 
-Following GA, we expect to release advanced features such as:
+Following GA, advanced features are being released, including:
 - Call Logs
 - Call Records
 - Transcriptions

articles/energy-data-services/how-to-enable-reservoir-ddms.md

@@ -13,6 +13,9 @@ ms.date: 02/08/2025
 # How to enable Reservoir DDMS (Preview)
 The Reservoir Domain Data Management Service (Reservoir DDMS) is a group of services that provides storage associated with seismic and well interpretation, structural modeling, geological modeling, and reservoir modeling including reservoir simulation input.
 
+> [!IMPORTANT]
+> Reservoir DMS is now a generally available service on Azure Data Manager for Energy. The service is available on all instances by default and do not require the steps below to make the service available. 
+
 [OSDU® Reservoir DDMS](https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/reservoir/home) is now available as a preview on the Azure Data Manager for Energy on both developer and standard tiers. This preview currently supports features available on the latest OSDU milestone version supported by Azure Data Manager for Energy. The standard tier instance supports testing for scale and performance of the Reservoir DMS functionality.
 
 The DDMS is fully integrated with all other OSDU® services on Azure Data Manager for Energy. However, during the preview phase, it isn't be enabled for all Azure Data Manager for Energy resources by default. Interested customers should submit a support request on the Azure portal providing the following details:
@@ -34,4 +37,4 @@ You're informed via support channels once your request is processed.
 To learn more about how to use Reservoir DDMS APIs, see:
 > [!div class="nextstepaction"]
 > [Tutorial: Use Reservoir DDMS websocket API endpoints](tutorial-reservoir-ddms-websocket.md)
-> [Tutorial: Use Reservoir DDMS API endpoints](tutorial-reservoir-ddms-apis.md)
+> [Tutorial: Use Reservoir DDMS API endpoints](tutorial-reservoir-ddms-apis.md)

articles/energy-data-services/index.yml

@@ -92,8 +92,6 @@ landingContent:
             url: how-to-register-external-data-services.md
           - text: How to enable legal tags restricted COO (Country of Origin)
             url: how-to-enable-legal-tags-restricted-country-of-origin.md
-          - text: How to enable Reservoir DDMS
-            url: how-to-enable-reservoir-ddms.md
   - title: Administration
     linkLists:
       - linkListType: how-to-guide

articles/expressroute/expressroute-locations-providers.md

@@ -70,7 +70,6 @@ The following table shows connectivity locations and the service providers for e
 | **Chennai** | Tata Communications | 2 | South India | &check; | BSNL<br/>DE-CIX<br/>Global CloudXchange (GCX)<br/>Lightstorm<br/>NTT Communications India Network Services Pvt Ltd<br/>Reliance JIO<br/>SIFY<br/>Tata Communications<br/>VodafoneIdea |
 | **Chennai2** | Airtel | 2 | South India | &check; | Airtel |
 | **Chicago** | [Equinix CH1](https://www.equinix.com/locations/americas-colocation/united-states-colocation/chicago-data-centers/ch1/) | 1 | North Central US | &check; | Aryaka Networks<br/>AT&T Dynamic Exchange<br/>AT&T NetBond<br/>British Telecom<br/>CenturyLink Cloud Connect<br/>Cogent<br/>Cologix<br/>Colt<br/>Console Connect (PCCW Global Limited)<br/>Comcast<br/>Coresite<br/>Equinix<br/>InterCloud<br/>Internet2<br/>Level 3 Communications<br/>Lightpath<br/>IPC<br/>Megaport<br/>Momentum Telecom<br/>PacketFabric<br/>Tata Communications<br/>Telia Carrier<br/>Verizon<br/>Vodafone<br/>Zayo |
-| **Chicago** | [Equinix CH1](https://www.equinix.com/locations/americas-colocation/united-states-colocation/chicago-data-centers/ch1/) | 1 | North Central US | &check; | Aryaka Networks<br/>AT&T Dynamic Exchange<br/>AT&T NetBond<br/>British Telecom<br/>CenturyLink Cloud Connect<br/>Cogent<br/>Cologix<br/>Colt<br/>Console Connect (PCCW Global Limited)<br/>Comcast<br/>Coresite<br/>Equinix<br/>InterCloud<br/>Internet2<br/>Level 3 Communications<br/>Lightpath<br/>IPC<br/>Megaport<br/>MODMC<br/>Momentum Telecom<br/>PacketFabric<br/>Tata Communications<br/>Telia Carrier<br/>Verizon<br/>Vodafone<br/>Zayo |
 | **Chicago2** | [CoreSite CH1](https://www.coresite.com/data-center/ch1-chicago-il) | 1 | North Central US | &check; | CenturyLink Cloud Connect<br/>CoreSite<br/>DE-CIX<br/>Megaport<br/>Momentum Telecom |
 | **Copenhagen** | [Digital Realty(Interxion) CPH1](https://www.digitalrealty.com/data-centers/emea/copenhagen/cph1) | 1 | &cross; | &check; | DE-CIX<br/>GlobalConnect<br/>Interxion (Digital Realty) |
 
@@ -171,7 +170,7 @@ The following table shows connectivity locations and the service providers for e
 | **Tel Aviv2** | SDS | 2 | Israel Central | &check; | Bezeq International<br/>Cellcom Fixed Line Communication (l.p.) |
 | **Tokyo** | [Equinix TY4](https://www.equinix.com/locations/asia-colocation/japan-colocation/tokyo-data-centers/ty4/) | 2 | Japan East | &check; | Aryaka Networks<br/>AT&T NetBond<br/>BBIX<br/>British Telecom<br/>CenturyLink Cloud Connect<br/>Colt<br/>Equinix<br/>Intercloud<br/>Internet Initiative Japan Inc. - IIJ<br/>KDDI<br/>Megaport<br/>NTT DOCOMO BUSINESS<br/>NTT DOCOMO BUSINESS - Flexible Interconnect (NTT Communications - Flexible Interconnect)<br/>NTT EAST<br/>Orange<br/>Softbank<br/>Verizon </br> |
 | **Tokyo2** | [AT TOKYO](https://www.attokyo.com/) | 2 | Japan East | &check; | AT TOKYO<br/>BBIX<br/>China Telecom Global<br/>China Unicom Global<br/>Colt<br/>Console Connect (PCCW Global Limited)<br/>DE-CIX<br/>Digital Realty<br/>Equinix<br/>Internet Initiative Japan Inc. - IIJ<br/>IPC<br/>IX Reach<br/>KDDI<br/>Megaport<br/>NTT DOCOMO BUSINESS - Flexible Interconnect (NTT Communications - Flexible Interconnect)<br/>Softbank<br/>Tokai Communications |
-| **Tokyo3** | [NEC](https://www.nec.com/en/global/solutions/cloud/inzai_datacenter.html) | 2 | Japan East | &check; | BBIX<br/NEC<br/>SCSK |
+| **Tokyo3** | [NEC](https://www.nec.com/en/global/solutions/cloud/inzai_datacenter.html) | 2 | Japan East | &check; | BBIX<br/>NEC<br/>SCSK |
 | **Toronto** | [Cologix TOR1](https://www.cologix.com/data-centers/toronto/tor1/) | 1 | Canada Central | &check; | AT&T NetBond<br/>Bell Canada<br/>CenturyLink Cloud Connect<br/>Cologix<br/>Equinix<br/>IX Reach<br/>Megaport<br/>Orange<br/>PacketFabric<br/>Tata Communications<br/>Telus<br/>Verizon<br/>Zayo |
 | **Toronto2** | [Allied REIT](https://alliedreit.com/city/toronto/) | 1 | Canada Central | &check; | Fibrenoire<br/>Megaport<br/>Telus<br/>Zayo |
 | **Vancouver** | [Cologix VAN1](https://www.cologix.com/data-centers/vancouver/van1/) | 1 | &cross; | &check; | Bell Canada<br/>Cologix<br/>Megaport<br/>Telus<br/>Zayo |