Microsoft Configuration

An organization using Microsoft to manage UC provisioning requires a number of different portals in a tenant: Azure, Microsoft 355 Admin Center, and (once users are licensed through Microsoft Office 365), a portal on the Microsoft Teams side for telephony. MS Exchange can also be added to the tenant.

VOSS Automate combines these functions into a single management interface, allowing service providers to import data from multiple Microsoft tenants and to manage these customers (or tenants) from a single portal and login.

The diagram describes the initial configuration required to integrate Microsoft with VOSS Automate:

  • You will need to install and configure a Microsoft Windows PowerShell Proxy server (one or more). This is to allow VOSS Automate to access Azure via the PowerShell. For details, see PowerShell Proxy Setup

  • Once the Microsoft Windows PowerShell service is installed, you will use the IP address and credentials of the proxy server to configure the Microsoft tenant.

    @startuml 'Microsoft Configuration Flowchart !include style.iuml start :[[../src/user/microsoft/pshell-proxy-setup.html PowerShell Proxy Setup]]; note right * Separate Proxy server setup * MS Azure IP, admin, users end note fork :Azure users synced into MS 365; fork again :Azure users synced into MS Teams; fork again :Azure users synced into MS Exchange; end fork :[[../src/user/microsoft/microsoft-device-mgt.html#microsoft-authentication-authorization-and-security-considerations Microsoft Authentication, Authorization, and Security Considerations]]; note right: authentication between MS 365, Teams and VOSS Automate :[[../src/user/microsoft/v4uc-msft-conn-params.html Go to VOSS Automate Microsoft Connection Parameters]]; note right: [[../src/user/concepts-ms-exchange.html MS Exchange option]] @enduml

Next Steps

VOSS Automate Configuration and Sync

Related Topics

Microsoft Overview

previous

Contact Center Management

next

Microsoft Subscribers