Merge pull request #225204 from MicrosoftDocs/release-ga-az-communications-gateway

Release Azure Communications Gateway

Author: v-alje

articles/azure-resource-manager/management/azure-subscription-service-limits.md

@@ -105,6 +105,18 @@ To learn more about limits on a more granular level, such as document size, quer
 
 [!INCLUDE [azure-cognitive-services-limits](../../../includes/azure-cognitive-services-limits.md)]
 
+## Azure Communications Gateway limits
+
+Some of the following default limits and quotas can be increased. To request a change, create a [change request](/azure/communications-gateway/request-changes.md) stating the limit you want to change.
+
+[!INCLUDE [communications-gateway-general-restrictions](../../communications-gateway/includes/communications-gateway-general-restrictions.md)]
+
+Azure Communications Gateway also has limits on the SIP signaling.
+
+[!INCLUDE [communications-gateway-sip-size-restrictions](../../communications-gateway/includes/communications-gateway-sip-size-restrictions.md)]
+
+[!INCLUDE [communications-gateway-sip-behavior-restrictions](../../communications-gateway/includes/communications-gateway-sip-behavior-restrictions.md)]
+
 ## Azure Container Apps limits
 
 For Azure Container Apps limits, see [Quotas in Azure Container Apps](../../container-apps/quotas.md).

articles/communications-gateway/deploy.md

@@ -0,0 +1,76 @@
+---
+title: Deploy Azure Communications Gateway 
+description: This article guides you through how to deploy an Azure Communications Gateway.
+author: rcdun
+ms.author: rdunstan
+ms.service: communications-gateway
+ms.topic: how-to 
+ms.date: 12/16/2022
+---
+
+# Deploy Azure Communications Gateway
+
+This article will guide you through creating an Azure Communications Gateway resource in Azure. You must configure this resource before you can deploy Azure Communications Gateway.
+
+## Prerequisites
+
+Carry out the steps detailed in [Prepare to deploy Azure Communications Gateway](prepare-to-deploy.md).
+
+## 1. Start creating the Azure Communications Gateway resource
+
+In this step, you'll create the Azure Communications Gateway resource.
+
+1. Sign in to the [Azure portal](https://azure.microsoft.com/).
+1. In the search bar at the top of the page, search for Communications Gateway and select **Communications Gateways**.  
+
+    :::image type="content" source="media/deploy/search.png" alt-text="Screenshot of the Azure portal. It shows the results of a search for Azure Communications Gateway.":::
+
+1. Select the **Create** option.
+
+    :::image type="content" source="media/deploy/create.png" alt-text="Screenshot of the Azure portal. Shows the existing Azure Communications Gateway. A Create button allows you to create more Azure Communications Gateways.":::
+
+1. Use the information you collected in [Collect Azure Communications Gateway resource values](prepare-to-deploy.md#6-collect-basic-information-for-deploying-an-azure-communications-gateway) to fill out the fields in the **Basics** configuration section and then select **Next: Service Regions**.
+
+    :::image type="content" source="media/deploy/basics.png" alt-text="Screenshot of the Create an Azure Communications Gateway portal, showing the Basics section.":::
+
+1. Use the information you collected in [Collect Service Regions configuration values](prepare-to-deploy.md#7-collect-service-regions-configuration-values) to fill out the fields in the **Service Regions** section and then select **Next: Tags**.
+1. (Optional) Configure tags for your Azure Communications Gateway resource: enter a **Name** and **Value** for each tag you want to create.
+1. Select **Review + create**.
+
+If you've entered your configuration correctly, you'll see a **Validation Passed** message at the top of your screen. Navigate to the **Review + create** section.
+
+If you haven't filled in the configuration correctly, you'll see an error message in the configuration section(s) containing the invalid configuration. Correct the invalid configuration by selecting the flagged section(s) and use the information within the error messages to correct invalid configuration before returning to the **Review + create** section.
+
+:::image type="content" source="media/deploy/failed-validation.png" alt-text="Screenshot of the Create an Azure Communications Gateway portal, showing a validation that failed due to missing information in the Contacts section.":::
+
+## 2. Submit your Azure Communications Gateway configuration
+
+Check your configuration and ensure it matches your requirements. If the configuration is correct, select **Create**.
+
+You now need to wait for your resource to be provisioned and connected to the Teams environment. Upon completion your onboarding team will reach out to you and the Provisioning Status filed on the resource overview will show as "Complete". We recommend you check in periodically to see if your resource has been provisioned. This process can take up to two weeks as updating ACLs in the Azure and Teams environments is done on a periodic basis.
+
+Once your resource has been provisioned, a message will appear saying **Your deployment is complete**. Select **Go to resource group**, and then check that your resource group contains the correct Azure Communications Gateway resource.
+
+:::image type="content" source="media/deploy/go-to-resource-group.png" alt-text="Screenshot of the Create an Azure Communications Gateway portal, showing a completed deployment screen.":::
+
+## 3. Complete the JSON onboarding file
+
+Your onboarding team will require additional information to complete your Operator Connect onboarding. If you're being onboarded to Operator Connect/Teams Phone Mobile by Microsoft, the onboarding team will reach out to you.
+Wait for your onboarding team to confirm that the process is complete before testing your portal access.
+
+## 4. Test your portal access
+
+Navigate to the [Operator Connect homepage](https://operatorconnect.microsoft.com/) and ensure you're able to sign in.
+
+## 5. Register your Fully Qualified Domain Name (FQDN)
+
+Your Azure Communications Gateway will require a custom domain name inside your Active Directory tenant. Follow this step to set up the custom domain name that Teams will use to recognize an Azure Communications Gateway that belongs to you.
+
+1. Navigate to your Azure Communications Gateway resource and select **Properties**. You'll see a field named **Domain name**. This name is your custom domain name.
+1. Complete the following procedure: [Add your custom domain name to Azure AD](/azure/active-directory/fundamentals/add-custom-domain).
+1. Share your DNS TXT record information with your onboarding team. Wait for your onboarding team to confirm that the DNS TXT record has been configured correctly.
+1. Complete the following procedure: [Verify your custom domain name](/azure/active-directory/fundamentals/add-custom-domain).
+
+## Next steps
+
+- [Prepare for live traffic with Azure Communications Gateway](prepare-for-live-traffic.md)

articles/communications-gateway/emergency-calling.md

@@ -0,0 +1,52 @@
+---
+title: Emergency Calling with Azure Communications Gateway
+description: Understand Azure Communications Gateway's support for emergency calling
+author: rcdun
+ms.author: rdunstan
+ms.service: communications-gateway
+ms.topic: conceptual
+ms.date: 01/09/2023
+ms.custom: template-concept
+---
+
+# Emergency calling with Azure Communications Gateway
+
+Azure Communications Gateway supports Operator Connect and Teams Phone Mobile subscribers making emergency calls from Microsoft Teams clients. This article describes how Azure Communications Gateway routes these calls to your network and the key facts you'll need to consider.
+
+## Overview of emergency calling with Azure Communications Gateway
+
+If a subscriber uses a Microsoft Teams client to make an emergency call and the subscriber's number is associated with Azure Communications Gateway, Microsoft Phone System routes the call to Azure Communications Gateway. The call has location information encoded in a PIDF-LO (Presence Information Data Format Location Object) SIP body.
+
+Unless you choose to route emergency calls directly to an Emergency Routing Service Provider (US only), Azure Communications Gateway routes emergency calls to your network with this PIDF-LO location information unaltered. It is your responsibility to ensure that these emergency calls are properly routed to an appropriate Public Safety Answering Point (PSAP). For more information on how Microsoft Teams handles emergency calls, see [the Microsoft Teams documentation on managing emergency calling](/microsoftteams/what-are-emergency-locations-addresses-and-call-routing#considerations-for-operator-connect).
+
+Microsoft Teams always sends location information on SIP INVITEs for emergency calls. This information can come from several sources, all supported by Azure Communications Gateway:
+
+- [Dynamic locations](/microsoftteams/configure-dynamic-emergency-calling), based on the location of the client used to make the call.
+  - Enterprise administrators must add physical locations associated with network connectivity into the Location Information Server (LIS) in Microsoft Teams.
+  - When Microsoft Teams clients make an emergency call, they obtain their physical location based on their network location.
+- Static locations that you assign to numbers.
+  - The Operator Connect API allows you to associate numbers with locations that enterprise administrators have already configured in the Microsoft Teams Admin Center as part of uploading numbers.
+  - Azure Communications Gateway's API Bridge Number Management Portal also allows you to associate numbers with locations during upload. You can also manage the locations associated with numbers after the numbers have been uploaded.
+- Static locations that your enterprise customers assign. When you upload numbers, you can choose whether enterprise administrators can modify the location information associated with each number.
+
+> [!NOTE]
+> If you are taking responsibility for assigning static locations to numbers, note that enterprise administrators must have created the locations within the Microsoft Teams Admin Center first.
+
+Azure Communications Gateway identifies emergency calls based on the dialing strings configured when you [deploy the Azure Communications Gateway resource](deploy.md). These strings will also be used by Microsoft Teams to identify emergency calls.
+
+## Emergency calling in the United States
+
+Within the United States, Microsoft Teams supports the Emergency Routing Service Providers (ERSPs) listed in the ["911 service providers" section of the list of Session Border Controllers certified for Direct Routing)](/microsoftteams/direct-routing-border-controllers). Azure Communications Gateway has been certified to interoperate with these ERSPs.
+
+You must route emergency calls to one of these ERSPs. If your network doesn't support PIDF-LO SIP bodies, Azure Communications Gateway can route emergency calls directly to your chosen ERSP. You must arrange this routing with your onboarding team.
+
+## Emergency calling with Teams Phone Mobile
+
+For Teams Phone Mobile subscribers, Azure Communications Gateway routes emergency calls from Microsoft Teams clients to your network in the same way as other originating calls. The call includes location information in accordance with the [emergency call considerations for Teams Phone Mobile](/microsoftteams/what-are-emergency-locations-addresses-and-call-routing#considerations-for-teams-phone-mobile).
+
+Your network must not route emergency calls from native dialers to Azure Communications Gateway or Microsoft Teams.
+
+## Next steps
+
+- Learn about [the key concepts in Microsoft Teams emergency calling](/microsoftteams/what-are-emergency-locations-addresses-and-call-routing).
+- Learn about [dynamic emergency calling in Microsoft Teams](/microsoftteams/configure-dynamic-emergency-calling).

articles/communications-gateway/includes/communications-gateway-general-restrictions.md

@@ -0,0 +1,13 @@
+---
+author: rcdun
+ms.author: rdunstan
+ms.service: communications-gateway
+ms.topic: include
+ms.date: 01/10/2022
+---
+
+The following restrictions apply to all Azure Communications Gateways:
+
+* All traffic must use IPv4.
+* All traffic must use TLS 1.2 or greater. Earlier versions aren't supported.
+* The number of active calls is limited to 15% of the number of Users assigned to the Azure Communications Gateway as defined in [Plan and manage costs for Azure Communications Gateway](/azure/communications-gateway/plan-and-manage-costs).

articles/communications-gateway/includes/communications-gateway-sip-behavior-restrictions.md

@@ -0,0 +1,13 @@
+---
+author: rcdun
+ms.author: rdunstan
+ms.service: communications-gateway
+ms.topic: include
+ms.date: 01/10/2022
+---
+
+Some endpoints might add parameters in the following headers to an in-dialog message when those parameters weren't present in the dialog-creating message. In that case, Azure Communications Gateway will strip them, because this behavior isn't permitted by RFC 3261.
+
+* Request URI
+* To header
+* From header

articles/communications-gateway/includes/communications-gateway-sip-size-restrictions.md

@@ -0,0 +1,20 @@
+---
+author: rcdun
+ms.author: rdunstan
+ms.service: communications-gateway
+ms.topic: include
+ms.date: 01/10/2022
+---
+
+|Resource|Limit|
+|--------|-----|
+|Maximum SIP message size| 10 Kilobytes|
+|Maximum length of an SDP message body| 128 Kilobytes|
+|Maximum length of request URI|256 Bytes|
+|Maximum length of Contact header URI| 256 Bytes|
+|Maximum length of the userinfo part of a URI| 256 Bytes|
+|Maximum length of domain name in From header|255 Bytes|
+|Maximum length of a SIP header's name| 32 Bytes|
+|Maximum length of a SIP body name| 64 Bytes|
+|Maximum length of a Supported, Require or Proxy-Require header| 256 Bytes|
+|Maximum length of a SIP option-tag| 32 Bytes|

articles/communications-gateway/index.yml

@@ -0,0 +1,69 @@
+### YamlMime:Landing
+
+title: Azure Communications Gateway documentation
+summary: Learn about Azure Communications Gateway. Azure Communications Gateway enables telecommunications operators to provide Operator Connect and Teams Phone Mobile services.
+
+metadata:
+  title: Azure Communications Gateway documentation
+  description: Learn about Azure Communications Gateway. Azure Communications Gateway enables telecommunications operators to provide Operator Connect and Teams Phone Mobile services.
+  ms.service: communications-gateway
+  ms.topic: landing-page
+  author: rcdun
+  ms.author: rdunstan
+  ms.date: 12/16/2022
+
+# linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | whats-new
+
+landingContent:
+
+  # Card
+  - title: Understand Azure Communications Gateway
+    linkLists:
+      - linkListType: overview
+        links:
+          - text: What is Azure Communications Gateway?
+            url: overview.md
+      - linkListType: concept
+        links:
+          - text: Interoperability with Microsoft Teams
+            url: interoperability.md
+          - text: Emergency calling
+            url: emergency-calling.md
+          - text: Reliability
+            url: reliability-communications-gateway.md
+          - text: Security
+            url: security.md
+
+  # Card
+  - title: Learn how to deploy Azure Communications Gateway
+    linkLists:
+      - linkListType: concept
+        links:
+          - text: Onboarding to Microsoft Teams 
+            url: onboarding.md
+      - linkListType: deploy
+        links:
+          - text: Prepare to deploy
+            url: prepare-to-deploy.md
+          - text: Deploy
+            url: deploy.md
+          - text: Prepare for live traffic
+            url: prepare-for-live-traffic.md
+
+  # Card
+  - title: Manage Azure Communications Gateway
+    linkLists:
+      - linkListType: concept
+        links:
+          - text: Monitoring Azure Communications Gateway
+            url: monitor-azure-communications-gateway.md
+      - linkListType: how-to-guide
+        links:
+          - text: Get support or request changes
+            url: request-changes.md
+          - text: Set up user roles
+            url: provision-user-roles.md
+          - text: Plan and manage costs
+            url: plan-and-manage-costs.md
+          - text: Rotate secrets
+            url: rotate-secrets.md