|
1 | 1 | ---
|
2 | 2 | title: Onboarding to Microsoft Teams Phone with Azure Communications Gateway
|
3 |
| -description: Understand the Azure Communications Gateway Basic Integration Included Benefit for onboarding to Operator Connect and your other options for onboarding |
| 3 | +description: Understand the Included Benefits and your other options for onboarding |
4 | 4 | author: rcdun
|
5 | 5 | ms.author: rdunstan
|
6 | 6 | ms.service: communications-gateway
|
7 | 7 | ms.topic: conceptual
|
8 |
| -ms.date: 01/18/2023 |
| 8 | +ms.date: 07/27/2023 |
9 | 9 | ms.custom: template-concept
|
10 | 10 | ---
|
11 | 11 |
|
12 |
| -# Onboarding to Microsoft Teams with Azure Communications Gateway |
| 12 | +# Onboarding with Included Benefits for Azure Communications Gateway |
13 | 13 |
|
14 |
| -To launch Operator Connect and/or Teams Phone Mobile, you'll need an onboarding partner. Launching requires changes to the Operator Connect or Teams Phone Mobile environments and your onboarding partner manages the integration process and coordinates with Microsoft Teams on your behalf. They can also help you design and set up your network for success. |
| 14 | +To launch Operator Connect and/or Teams Phone Mobile, you need an onboarding partner. Launching requires changes to the Operator Connect or Teams Phone Mobile environments and your onboarding partner manages the integration process and coordinates with Microsoft Teams on your behalf. They can also help you design and set up your network for success. |
15 | 15 |
|
16 |
| -If you're launching Operator Connect, Azure Communications Gateway includes an off-the-shelf onboarding service called the Basic Integration Included Benefit. It's suitable for simple Operator Connect use cases. |
| 16 | +We provide a customer success program and onboarding service called Included Benefits for operators deploying Azure Communications Gateway. We work with your team to enable rapid and effective solution design and deployment. The program includes tailored guidance from Azure for Operators engineers, using proven practices and architectural guides. |
17 | 17 |
|
18 |
| -If you're launching Teams Phone Mobile, you're not eligible for the Basic Integration Included Benefit. See [Alternatives to the Basic Integration Included Benefit](#alternatives-to-the-basic-integration-included-benefit). |
| 18 | +## Eligibility for Included Benefits and alternatives |
19 | 19 |
|
20 |
| -## Onboarding with the Basic Integration Included Benefit for Operator Connect |
| 20 | +Included Benefits is available to operator customers who: |
21 | 21 |
|
22 |
| -The Basic Integration Included Benefit (BIIB) helps you to onboard customers to your Microsoft Teams Operator Connect offering as quickly as possible. You'll need to meet the [eligibility requirements](#eligibility-for-the-basic-integration-included-benefit). |
| 22 | +- Have an active paid Azure subscription. |
| 23 | +- Have a defined project using Azure Communications Gateway with intent to deploy. A defined project has an executive sponsor, committed customer/partner resources, established success metrics, and clear timelines for start and end of the project. |
| 24 | +- Are located in a country/region supported by Azure Communications Gateway. Engagements are in English (although we may offer engagements in your local language, depending on the availability of our teams). |
23 | 25 |
|
24 |
| -If you're eligible, we'll assign the following people as your onboarding team. |
| 26 | +There's no cost to you for the Included Benefits program. |
25 | 27 |
|
26 |
| -- A remote **Project Manager** as a single point of contact. The Project Manager is responsible for communicating the schedule and keeping you up to date with your onboarding status. |
27 |
| -- Microsoft **Delivery Consultants** and other technical personnel, led by a **Technical Delivery Manager**. These people guide and support you through the onboarding process for Microsoft Teams Operator Connect. The process includes providing and certifying the Operator Connect SBC functionality and launching your Operator Connect service in the Teams Admin Center. |
| 28 | +If your requirements exceed the scope of the program or you fail to meet your responsibilities, at any point we might ask you to: |
28 | 29 |
|
29 |
| -### Eligibility for the Basic Integration Included Benefit |
| 30 | +- Contact your Microsoft sales representative to arrange extra services. |
| 31 | +- Find your own partner able to meet your needs (for example a System Integrator). |
30 | 32 |
|
31 |
| -To be eligible for the BIIB, you must first deploy an Azure Communications Gateway resource. In addition: |
| 33 | +## Process overview for Included Benefits |
32 | 34 |
|
33 |
| -- You must be launching Microsoft Teams Operator Connect for fixed-line calls (not Teams Phone Mobile). |
34 |
| -- Your network must be capable of meeting the [reliability requirements for Azure Communications Gateway](reliability-communications-gateway.md). |
35 |
| -- You must not have more than two Azure service regions (the regions containing the voice and API infrastructure for traffic). |
36 |
| -- You must not require any interworking options that aren't listed in the [interoperability description](interoperability.md). |
37 |
| -- You must not require any API customization as part of the API Bridge feature (if you choose to deploy the API Bridge). |
| 35 | +Azure for Operators partners with you to drive your business outcomes and success. Our goal is to empower you to deliver a new breed of solutions that meet the fast-changing needs of business today and in the future. To achieve this goal, Included Benefits takes a solution-centric approach, providing you with design principles and tools for your solutions: we work with you from design to deployment in a production environment. When you use Included Benefits to help accelerate and deploy solutions on Azure, there are three phases involved in the process: |
38 | 36 |
|
39 |
| -If you don't meet these requirements, see [Alternatives to the Basic Integration Included Benefit](#alternatives-to-the-basic-integration-included-benefit). |
| 37 | +### Phase 1: Discovery |
40 | 38 |
|
41 |
| -If we (Microsoft) determine at our sole discretion that your integration needs are unusually complex, we might: |
| 39 | +Once you've identified your Azure Communications Gateway project, you can ask your account team to nominate your project for Included Benefits. The Included Benefits team works with you to identify key stakeholders, understand the vision/goals, and assess the architectural needs for problems you're trying to solve. |
42 | 40 |
|
43 |
| -- Decline to provide the BIIB. |
44 |
| -- Stop providing the BIIB, even if we've already started providing it. |
| 41 | +In this phase, we establish eligibility, scope and conditions of success for the project. |
45 | 42 |
|
46 |
| -This limitation applies even if you're otherwise eligible. |
| 43 | +### Phase 2: Solution enablement |
47 | 44 |
|
48 |
| -We might also stop providing the BIIB if you don't meet [your obligations with the Basic Integration Included Benefit](#your-obligations-with-the-basic-integration-included-benefit), including making timely responses to questions and fulfilling dependencies. |
| 45 | +If your project is approved, the Included Benefits team carries out architectural design reviews and delivers solution enablement guidance by sharing proven practices and design principles for the solution. |
49 | 46 |
|
50 |
| -### Phases of the Basic Integration Included Benefit |
| 47 | +A typical project might include the following engagements: |
51 | 48 |
|
52 |
| -When you've deployed your Azure Communications Gateway resource, your onboarding team will help you to ensure that Azure Communications Gateway and your network are properly configured for Operator Connect. Your onboarding team will then help you through the Operator Connect onboarding process, so that your service is launched in the Teams Admin Center. |
| 49 | +- Technical talks and workshops: subject matter deep dives and best practices to accelerate your deployment. These meetings often provide an overview of available documentation and admin consoles. |
| 50 | +- Review of your architecture and design with Azure Communications Gateway. |
| 51 | +- Checkpoint meetings: weekly or biweekly touchpoints to ensure that your deployment is progressing to completion. |
53 | 52 |
|
54 |
| -The BIIB has three phases. During these phases, you'll be responsible for some steps. See [Your obligations with the Basic Integration Included Benefit](#your-obligations-with-the-basic-integration-included-benefit). |
| 53 | +### Phase 3: Deployment |
55 | 54 |
|
56 |
| -#### Phase 1: gathering information |
| 55 | +The Included Benefits team supports your in-house resources (your teams and people) or a partner to successfully deploy Azure Communications Gateway into production. |
57 | 56 |
|
58 |
| -We'll share the Teams Operator Connect specification documents (for example, for network connectivity) if you don't already have access to them. We'll also provide an Operator Connect onboarding form and a proposed test plan. When you've given us the information listed in the onboarding form, your onboarding team will work with you to create a project timeline describing your path to launching in the Teams Admin Center. |
| 57 | +A typical project might include the following engagements: |
59 | 58 |
|
60 |
| -#### Phase 2: preparing Azure Communications Gateway and your networks |
| 59 | +- Integration testing: support and advice for troubleshooting of issues identified with the solution. |
| 60 | +- Help gathering artifacts for Microsoft Teams Operator Connect Certification (if applicable) |
61 | 61 |
|
62 |
| -We'll use the information you provided with the onboarding form to set up Azure Communications Gateway. We'll also provide guidance on preparing your own environment for Azure Communications Gateway. |
| 62 | +## Scope of Included Benefits |
63 | 63 |
|
64 |
| -#### Phase 3: preparing for live traffic |
| 64 | +Included Benefits is aimed at standard deployments of Azure Communications Gateway. It covers: |
65 | 65 |
|
66 |
| -Your onboarding team will work through the steps described in [Prepare for live traffic with Azure Communications Gateway](prepare-for-live-traffic.md) with you. As part of these steps, we'll: |
| 66 | +- Initial deployment of Azure Communications Gateway and integration into operator's production network |
| 67 | +- If you're launching Microsoft Teams Operator Connect, fulfilling the role of an Operator Connect Accelerator by guiding and supporting you through the onboarding process for Microsoft Teams Operator Connect. |
67 | 68 |
|
68 |
| - - Work through the test plan we agreed, with your help. |
69 |
| - - Provide training on the Azure Communications Gateway solution. Training topics include: |
70 |
| - - A technical overview of the Azure Communications Gateway platform. |
71 |
| - - How your engineering and operations staff can interact with Azure Communications Gateway and Operator Connect. |
72 |
| - - How your teams can get support for Azure Communications Gateway and Operator Connect. |
73 |
| - - Help you to prepare for launch. |
| 69 | +## Responsibilities with Included Benefits |
74 | 70 |
|
75 |
| -### Your obligations with the Basic Integration Included Benefit |
| 71 | +We provide: |
76 | 72 |
|
77 |
| -You're responsible for: |
| 73 | +- Guidance on: |
| 74 | + - Enablement of Azure Communications Gateway (including remote support). |
| 75 | + - Configuration tasks and integration testing. |
| 76 | + - Azure platform configuration. |
| 77 | +- Architectural guidance and design principles for eligible solutions. |
| 78 | +- Resources committed to making your project successful. |
78 | 79 |
|
79 |
| -- Arranging Microsoft Azure Peering Service (MAPS) connectivity. If you haven't finished rolling out MAPS yet, you must have started the roll-out and have a known delivery date. |
80 |
| -- Signing the Operator Connect agreement. |
81 |
| -- Providing someone as a single point-of-contact to assist us in collecting information and coordinating your resources. This person must have the authority to review and approve deliverables, and otherwise ensure that these responsibilities are carried out. |
82 |
| -- Completing the onboarding form after we've supplied it. |
83 |
| -- Providing test numbers and working with your onboarding team to run the test plan, including testing from your network to find call flow integration issues. |
84 |
| -- Providing timely responses to questions, issues and dependencies to ensure the project finishes on time. |
85 |
| -- Configuring your Operator Connect and Azure environments as described in [Prepare to deploy Azure Communications Gateway](prepare-to-deploy.md), [Deploy Azure Communications Gateway](deploy.md) and [Prepare for live traffic with Azure Communications Gateway](prepare-for-live-traffic.md). |
86 |
| -- Ensuring that your network is compliant with the Microsoft Teams _Network Connectivity Specification_ and _Operational Excellence Specification_, and any other specifications provided by Microsoft Teams. |
87 |
| -- Ensuring that your network engineers watch the training that your onboarding team provides. |
| 80 | +Your responsibilities include: |
88 | 81 |
|
89 |
| -## Alternatives to the Basic Integration Included Benefit |
90 |
| - |
91 |
| -If you're not eligible for the Basic Integration Included Benefit (because you're deploying Teams Phone Mobile or you don't meet the [eligibility requirements](#eligibility-for-the-basic-integration-included-benefit)), you must arrange onboarding separately. You can: |
92 |
| - |
93 |
| -- Contact your Microsoft sales representative to arrange onboarding through Microsoft. |
94 |
| -- Find your own onboarding partner. |
| 82 | +- Providing someone as a single point-of-contact to assist us in collecting information and coordinating your resources (your teams and people). This person must have the authority to review and approve deliverables, and otherwise ensure that these responsibilities are carried out. |
| 83 | +- Providing timely responses to questions, issues, and dependencies to ensure the project finishes on time. |
| 84 | +- Creating architectural documentation and technical documentation specific to your organization. |
| 85 | +- Hands-on administration, support, and deployment on Azure. |
| 86 | +- Producing any reports, presentations, and meeting minutes that are specific to your organization. |
| 87 | +- Overall program management and project management for your resources. |
| 88 | +- Managing your deployment, third-party suppliers (for example, any system integrators or provisioning partners), and your suppliers' equipment, as necessary. |
| 89 | +- Providing test numbers, devices and testing from your network to find integration issues. |
| 90 | +- Demos, POCs or extra testing specific to your organization. |
95 | 91 |
|
96 | 92 | ## Next steps
|
97 | 93 |
|
|
0 commit comments