| Home | About | Considerations | Deployment Guide | Support |
|---|
Important
These samples are provided "as is" without warranty of any kind. Microsoft further disclaims all implied warranties including without limitation any implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the samples remains with you. In no event shall Microsoft or its suppliers be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the samples, even if Microsoft has been advised of the possibility of such damages. Because some states do not allow the exclusion or limitation of liability for consequential or incidental damages, the above limitation may not apply to you.
Shared Calling greater simplifies and accelerates the deployment of Teams Phone. A shared phone number is used and applied to multiple Teams Phone users via a single policy configuration.
- Quick and easy to deploy.
- Makes the most of your Teams Phone licensing as part of E5 or standalone.
- Risk free as existing telephony can see be used in parallel.
- Works with all PSTN connectivity options.
- Existing telephone numbers can be consolidated or migrated later (backfilled) as part of a wider telephony transformation strategy.
- Can be combined as part of a cost reduction. i.e. not removing telephony access for low and no usage telephony users.
Instead of assigning a phone number to every user, you use the phone number of a resource account associated with an Auto attendant for inbound and outbound PSTN calls. The Shared Calling policy configures the resource account used for outbound calls and emergency numbers that are used as emergency callback numbers.
| Page | About |
|---|---|
| Author | Rob Watts (@robwatts365) |
| Version | 1.0 |
| Date | 25/01/2024 |