Merge pull request #16231 from MicrosoftDocs/main

Publish main to live, 12/17/24, 3:30 PM PT

Teams/cloud-voice-landing-page.md

@@ -3,7 +3,7 @@ title: Plan your voice solution in Microsoft Teams
 author: sfrancis206
 ms.author: scottfrancis
 manager: pamgreen
-ms.date: 08/03/2023
+ms.date: 12/17/2024
 ms.topic: article
 ms.service: msteams
 audience: admin
@@ -38,19 +38,22 @@ You might want the simplest solution—Microsoft Teams Phone with Calling Pl
 
 If you answer yes to the following, then Teams Phone with Calling Plan is the right solution for you:
 
-- Calling Plan is available in your region.
+- Calling Plan is available in your region. To confirm Calling Plan availability, see [Confirm Microsoft Calling Plan availability](calling-plan-overview.md).
 - You don't need to retain your current PSTN carrier.
 - You want to use Microsoft-managed access to the PSTN.
 
-If you’re a small to medium business (300 or fewer people), Microsoft now bundles Teams Phone with a Domestic Calling Plan. 
+If you're a small to medium business (300 or fewer people), Microsoft now bundles Teams Phone with a Domestic Calling Plan. 
 
-However, your situation might be more complex. For example, you might have offices in locations where Calling Plan isn't available. Or you might need a combination solution that supports a complex, multi-national deployment, with different requirements for different geographic locations. Microsoft supports a combination of solutions:
+However, your situation might be more complex. For example, you might have offices in locations where Calling Plan isn't available. Or you might need to accommodate existing, on-premises telephony infrastructure. Microsoft can solve for any PSTN or on-premises integration, with a variety of integration options.
 
 - Teams Phone with Calling Plan
 - Teams Phone with your own PSTN carrier with Operator Connect
-- Teams Phone with your own PSTN mobile carrier with Teams Phone Mobile 
+- Teams Phone with your own PSTN mobile carrier with Teams Phone Mobile
 - Teams Phone  with your own PSTN carrier with Direct Routing
-- A combination solution that uses Teams Phone with Calling Plan, Teams Phone with Operator Connect, and/or Teams Phone with Direct Routing
+
+You aren't limited to one integration. Just because you have a portion of users who are located in a country or region where Microsoft doesn't have a Calling Plan option doesn't mean all of your users have to be served by the one solution for those remote users.
+
+You can have a combination solution that uses Teams Phone with Calling Plan, Teams Phone with Operator Connect, Teams Phone with Teams Phone Mobile, and/or Teams Phone with Direct Routing.
 
 For a visual summary of all the voice solution options, see the voice solutions poster.
 
@@ -61,28 +64,34 @@ If you're interested in PSTN conferencing for meetings, you'll want to read abou
 
 ## What do you need to read?
 
-**Required for all.** Some of the sections in this article pertain to all organizations. For example, everyone should read about Teams Phone and understand the options for connecting to the Public Switched Telephone Network (PSTN).
+### Required for all
+
+Some of the sections in this article pertain to all organizations. For example, everyone should read about Teams Phone and understand the options for connecting to the Public Switched Telephone Network (PSTN).
 
 | Required for all | Description |
 | :------------|:-------|
 | [**Teams Phone**](#teams-phone) | Microsoft's technology for enabling call control and Private Branch Exchange (PBX) capabilities in the Microsoft 365 cloud with Microsoft Teams. |
 | [**Public Switched Telephone Network (PSTN) connectivity options**](#public-switched-telephone-network-connectivity-options) | Choose Microsoft as your telephony carrier or connect your own telephony carrier to Microsoft Teams by using Operator Connect or Direct Routing. Combined with Teams Phone, PSTN connectivity options enable your users to make phone calls all over the world.|
 
-**Depending on your requirements.** Some of the sections in this and related articles are pertinent depending on your existing deployment and requirements. For example, Location-Based Routing is only required for Direct Routing customers in geographic locations that do not allow toll bypass.
+### Depending on your requirements
 
-Consider which of these other configurations you might need:
+Next, consider which of these other configurations you might need:
 
 ![Diagram 2 shows other voice components, such as Phone numbers from Microsoft, Dial plans and call routing, and so on.](media/voice-consider-additional-components.png)
 
+Some of the sections in this and related articles are pertinent depending on your existing deployment and requirements, for example:
+
+- **Location-Based Routing** is only required for Direct Routing customers in geographic locations that don't allow toll bypass.
+- **Phone number management** is only required for Microsoft Calling Plan customers.
+
 | Depending on your requirements | Description |
 | :------------|:-------|
 | [**Phone number management**](pstn-connectivity.md#phone-number-management) | How to get and manage phone numbers differs depending on your PSTN connectivity option. Read this section if you need to obtain phone numbers, transfer existing numbers, obtain service numbers, and so on. |
 | [**Call routing and dial plans**](pstn-connectivity.md#call-routing-and-dial-plans) | How to configure and manage dial plans that translate dialed phone numbers into an alternate format (typically E.164 format) for call authorization and call routing. Read this section if you need to understand what dial plans are and whether you need to specify dial plans for your organization.|
 | [**Emergency calling**](pstn-connectivity.md#emergency-calling) | How to manage and configure emergency calling differs depending on your PSTN connectivity option. Read this section if you need to understand how to manage emergency calling for your organization. |
-| [**Location-Based Routing for Direct Routing**](pstn-connectivity.md#location-based-routing-for-direct-routing) |How to use Location-Based Routing (LBR) to restrict toll bypass for Microsoft Teams users based on their geographic location. Read this section if your organization is using Direct Routing at a location that doesn't allow toll bypass.
+| [**Location-Based Routing for Direct Routing**](pstn-connectivity.md#location-based-routing-for-direct-routing) |How to use Location-Based Routing (LBR) to restrict toll bypass for Microsoft Teams users based on their geographic location. Read this section if your organization is using Direct Routing at a location that doesn't allow toll bypass. |
 | [**Network topology for cloud voice features**](pstn-connectivity.md#network-topology-for-voice-features) | If your organization is deploying Location-Based Routing (LBR) for Direct Routing or dynamic emergency calling, you must configure network settings for these features in Microsoft Teams. Read this section if you're implementing LBR for Direct Routing, or if you're implementing dynamic emergency calling with Calling Plan or Direct Routing. |
-| [**Migrate your existing voice solution**](#migrate-your-existing-voice-solution-to-teams) | What you need to think about when migrating your voice solution to Teams.  Read this section if you're migrating from an existing voice solution to Teams. 
-
+| [**Upgrade your existing Skype for Business voice solution**](#upgrade-your-existing-skype-for-business-voice-solution-to-teams) | What you need to think about when upgrading your voice solution to Teams. Read this section if you're upgrading from an existing Skype for Business deployment to Teams. |
 
 ## Teams Phone
 
@@ -132,6 +141,7 @@ For more information about Cloud Voicemail and its configuration, see the follow
 
 - [Set up Cloud Voicemail](set-up-phone-system-voicemail.md)
 - [Manage voicemail policies](manage-voicemail-policies.md)
+- [Manage voicemail settings](manage-voicemail-settings.md)
 
 ### Calling identity
 
@@ -153,7 +163,7 @@ You can choose a combination of options, which enables you to design a solution
 
 Most Teams Phone features are the same regardless of the PSTN connectivity option you choose. There are some differences in functionality, however, that affect how you configure certain Teams Phone features, such as call routing and emergency calling. For more information about PSTN connectivity options and configuration considerations, see [PSTN connectivity options](pstn-connectivity.md).
 
-## Migrate your existing voice solution to Teams
+## Upgrade your existing Skype for Business voice solution to Teams
 
 For an organization that is upgrading to Teams, the ultimate goal is to move all users to TeamsOnly mode. Using Teams Phone is only supported when the user is in TeamsOnly mode. If you need basic information about upgrading to Teams, start here:
 
@@ -163,6 +173,4 @@ For an organization that is upgrading to Teams, the ultimate goal is to move all
 
 For guidance on planning a Teams voice solution as part as your overall plan to upgrade to Teams, see [PSTN considerations for upgrading to Teams from Skype for Business on-premises](upgrade-to-teams-on-prem-pstn-considerations.md).
 
-For more information about how to implement your voice migration, see the [Contoso voice migration case study](voice-case-study-overview.md). The case study describes how a fictional multi-national corporation, Contoso, implemented a Teams voice solution for their organization. 
-
-
+For more information about how to implement your voice migration, see the [Contoso voice migration case study](voice-case-study-overview.md). The case study describes how a fictional multi-national corporation, Contoso, implemented a Teams voice solution for their organization.

Teams/manage-phone-numbers-landing-page.md

@@ -3,8 +3,8 @@ title: "Manage phone numbers for your organization"
 author: sfrancis206
 ms.author: scottfrancis
 manager: pamgreen
-ms.reviewer: davlick, roykuntz, jenstr
-ms.date: 08/10/2023
+ms.reviewer: pavellatif
+ms.date: 12/17/2024
 ms.topic: conceptual
 ms.assetid: 6b61cb3c-361c-48a8-a9ef-d81bddde27bb
 ms.tgt.pltfrm: cloud
@@ -65,43 +65,50 @@ How you acquire and manage telephone numbers differs depending on your Public Sw
 ## User telephone numbers
 
 There are two types of user telephone numbers, which can be assigned to users in your organization:  
-    
+
 - **Geographic numbers** have a relationship to a geographic area and are the most common. For example, geographic telephone numbers in most cases can only be used within a certain address, city, state, or region of the country/region.
-
-- **Non-geographic numbers** are known as national numbers or sometimes VoIP numbers. These numbers don't have a relationship to a geographic area within a country/region. For example, non-geographic numbers often have the same cost when calling the number from anywhere within the country/region. Also, some countries/regions, such as Denmark, only have non-geographic numbers available.
 
+- **Non-geographic numbers** are known as national numbers or sometimes VoIP numbers. These numbers don't have a relationship to a geographic area within a country/region. For example, non-geographic numbers often have the same cost when calling the number from anywhere within the country/region. Also, some countries/regions, such as Denmark, only have non-geographic numbers available.
 
 ## Service telephone numbers  
 
-This section describes service numbers available from Microsoft that are included in your licensing. For information about service numbers provided by Operator Connect or Direct Routing, contact your provider. 
+This section describes service numbers available from Microsoft that are included in your licensing. For information about service numbers provided by Operator Connect or Direct Routing, contact your provider.
 
 There are two types of service telephone numbers provided by Microsoft--toll and toll-free--which can be assigned to services such as Audio Conferencing, Auto Attendants, or Call Queues. Service numbers have a higher concurrent call capacity than user numbers. Service number availability varies by country/region and the type of number (whether it's a toll or toll-free number). Microsoft’s telephony licenses in each country/region dictate what the number can be used for.
-    
- - **Toll service numbers** - There are two types of toll service numbers, which may incur a toll cost to the caller:
-    
-   - **Geographic numbers** Geographic numbers have a relationship to a geographic area. For example, geographic telephone numbers in most cases can only be used within a certain address, city, state, or region of the country.
-        
-   - **Non-geographic numbers** Non-geographic numbers are national numbers that don't have a relationship to a geographic area within a country/region. For example, non-geographic numbers often have the same cost when calling the number from anywhere within the country/region.
-   
+
+- **Toll service numbers** - There are two types of toll service numbers, which may incur a toll cost to the caller:
+
+  - **Geographic numbers** Geographic numbers have a relationship to a geographic area. For example, geographic telephone numbers in most cases can only be used within a certain address, city, state, or region of the country.
+
+  - **Non-geographic numbers** Non-geographic numbers are national numbers that don't have a relationship to a geographic area within a country/region. For example, non-geographic numbers often have the same cost when calling the number from anywhere within the country/region.
+
 - **Toll-free service numbers** - These service numbers don't typically incur a toll cost to the caller. Teams provides national toll-free numbers in over 60 countries/regions.
-    
+
     > [!CAUTION]
     > Some countries/regions and originating number types, such as calls originating from mobile phones, may in some cases incur a toll cost to the caller. 
 
 ## Where phone numbers are managed
 
 Where and how numbers are managed depend on the PSTN connectivity option:
 
-- Microsoft Calling Plan and Operator Connect phone numbers can be managed only in Microsoft 365.
+### Microsoft Calling Plan, Operator Connect, and Teams Phone Mobile
+
+Microsoft Calling Plan, Operator Connect, and Teams Phone Mobile phone numbers can be managed in the following interfaces:
+
+- Teams admin center (TAC)
+- Teams PowerShell
+- On-premises Active Directory
 
-- Direct Routing phone numbers can be managed in the on-premises Active Directory or in Microsoft 365 as described in the following sections.
+To review more details, see [Manage phone numbers for users](assign-change-or-remove-a-phone-number-for-a-user.md)
 
 ### Direct Routing numbers managed in an on-premises Active Directory
 
+Direct Routing phone numbers can be managed in on-premises Active Directory or in Microsoft 365.
+
 If you have or had a Skype for Business Server hybrid deployment,
 your on-premises Active Directory is most likely synchronizing with Microsoft 365. This means that directory attributes on user and resource accounts are managed in the on-premises Active Directory and synchronized into Microsoft 365.
 
-If the Direct Routing phone number is managed on the user or resource account in the on-premises Active Directory, the msRTCSIP-Line parameter on the account contains a value. You can use a tool such as ADSI Edit to view the msRTCSIP-Line parameter for a user or resource account that has a Direct Routing phone number assigned in on-premises Active Directory.   
+If the Direct Routing phone number is managed on the user or resource account in the on-premises Active Directory, the msRTCSIP-Line parameter on the account contains a value. You can use a tool such as ADSI Edit to view the msRTCSIP-Line parameter for a user or resource account that has a Direct Routing phone number assigned in on-premises Active Directory.
 
 After this parameter is automatically synchronized to the user or resource account in Microsoft 365 through the directory synchronization process (Microsoft Entra Connect), you can view the phone number by looking at the OnPremLineURi parameter in the output from the [Get-CsOnlineUser](/powershell/module/teams/get-csonlineuser) cmdlet.
 
@@ -112,16 +119,20 @@ After this parameter is automatically synchronized to the user or resource accou
 
 ### Direct Routing numbers managed in Microsoft 365
 
-If you're not managing Direct Routing phone numbers in the on-premises Active Directory, then they're managed in Microsoft 365. Because the phone numbers are not synching to Microsoft 365, they're not visible in the OnPremLineUri parameter in the output from the Get-CsOnlineUser cmdlet  run for the user or resource account.
+If you're not managing Direct Routing phone numbers in the on-premises Active Directory, then they're only managed in Microsoft 365. Because the phone numbers are not synching from on-premises to Microsoft 365, there is no visible value in the OnPremLineUri parameter in the output from the Get-CsOnlineUser cmdlet run for the user or resource account.
+
+You can manage Direct Routing numbers in Microsoft 365 with Teams Powershell, using the [Set-CsPhoneNumberAssignment](/powershell/module/teams/set-csphonenumberassignment) and [Get-CsPhoneNumberAssignment](/powershell/module/teams/get-csphonenumberassignment) cmdlets.
 
 ### Direct Routing numbers managed in both an on-premises Active Directory and Microsoft 365
 
-It's possible to manage Direct Routing phone numbers of some user and resource accounts in an on-premises Active Directory and Direct Routing phone numbers of other accounts in Microsoft 365. This capability depends on whether the attribute msRTCSIP-Line is set on the user or resource account in the on-premises Active Directory.    
+It's possible to manage Direct Routing phone numbers of some user and resource accounts in an on-premises Active Directory and Direct Routing phone numbers of other accounts in Microsoft 365. This capability depends on whether the attribute msRTCSIP-Line is set on the user or resource account in the on-premises Active Directory.
 
 ### Change where Direct Routing phone numbers are managed
 
-To change where a Direct Routing phone number is managed, you need to remove the phone number from the msRTCSIP-Line attribute on the user or resource account in the on-premises Active Directory.   
+To change where a Direct Routing phone number is managed, you need to remove the phone number from the msRTCSIP-Line attribute on the user or resource account in the on-premises Active Directory.
+
+Note that the phone number needs to be re-assigned to the user or resource account in Microsoft 365.
 
-For more information, see [Clear Skype for Business attributes for all on-premises users in Active Directory](/skypeforbusiness/hybrid/cloud-consolidation-managing-attributes#method-2---clear-skype-for-business-attributes-for-all-on-premises-users-in-active-directory.md). Note that the phone number needs to be re-assigned to the user or resource account in Microsoft 365.
+After the removal has been synchronized to Microsoft 365, the OnPremLineUri attribute in the output from Get-CsOnlineUser on the user or resource account will be empty.
 
-After the removal has been synchronized to Microsoft 365, the OnPremLineUri attribute in the output from Get-CsOnlineUser on the user or resource account will be empty. 
+For more information, see [Clear Skype for Business attributes for all on-premises users in Active Directory](/skypeforbusiness/hybrid/cloud-consolidation-managing-attributes#method-2---clear-skype-for-business-attributes-for-all-on-premises-users-in-active-directory.md).