Howto:Microsoft Office 365 Recommended Product Testreport

From innovaphone wiki
Jump to navigation Jump to search

General Information

  • Product name: Office 365
  • Vendor: Microsoft
  • innovaphone Firmware: v10 sr10

The objective of this article it's to test the Office 365 Solution together with Innovaphone Applications like innovaphone Exchange Calender Connector, innovaphone FaxServer and myPBX Office Integration.

How to configure this applications together with Office 365 and if there is any limitations.

Current test state

This product is being tested right now. The test is not yet completed.


Configured Scenario

Important Components and Requirements

  • Office 365 Small Business Premium Plan.
  • Office 365 System Requirements can be found -> Here
  • innovaphone myPBX Launcher
  • innovaphone PBX v10
  • innovaphone Exchange Connector Application

myPBX Office Integration

Installation & Configuration of the vendor Software

In order to have myPBX Office Integration it's required to install the Office Applications.

The Office Applications are only available for some specific Office 365 Subscription Plans you could find a comparison table for the business plans here.

To install the office applications the user just login into the portal.office.com and click on the shortcut Download Software and be able to download the full package. Microsoft Install Office Guide.


Installation & Configuration of the innovaphone components

First install the myPBX launcher at the Windows PC and define the myPBX UC Client as Office Presence Provider like explained at Concept myPBX Office2010 Integration.

The system Name of the PBX should be equal to the office 365 Domain Name and also we should enable the flag "Use as Domain".

The "Name" field at the PBX User Object should match also with the Office 365 User so the Email address can be identical.

Example: Office 365 User with email rba@innovaphoneAG.onmicrosoft.com should match with User Object with name field equal to "rba".


Test Results

Tested feature Result
Presence Updates at Microsoft Desktop App Contact Info. OK
Instant Messaging started from Desktop Microsoft App. OK
Start calls from Microsoft Desktop App. OK
Presence Updates at Microsoft Web App Contact Info. NOK


innovaphone Exchange Calender Connector

Installation & Configuration of the vendor Software

In order to be able Exchange Calender Connector connect to the Exchange Online EWS we need first to find what is the Exchange Online Server Address. The URL of Exchange Online Web Service is a URL like "https://" + "Server name" + "/EWS/Exchange.amsx", for example, https://pod51024.outlook.com/ews/exchange.amsx.

How to find the Exchange Server address you could find some indications Office365 Community Answers.

Also similar to what it's done with Local Exchange Installations it's required that each User change their permissions for vieweing Free/Busy Information at Outlook Calender Options.

With Office365 we could only find this option using the Outlook Desktop App and not the Outlook Web App, description how to find this option could be find at Concept Exchange Calender Connector Article

If the Administrator doesn't wish to give this task to each User of his organization or change this permissions via the Outlook Client it's possible to find similar solution to configure it using PowerShell Scripts, here is an solution example.


Installation & Configuration of the innovaphone components

NTML Authentication it's not supported by Office 365 Exchange Online Server, so it's necessary to use basic Authentication method to connect to Exchange Online EWS.

This feature was introduced with innovaphone Exchange Connector v10sr11 like described here.



innovaphone FaxServer

Installation & Configuration of the vendor Software

Installation & Configuration of the innovaphone components

Product Test

FIXME: Note: Possible test results are Ok, Nok, Not tested, N/A(not available). Ok, Nok, N/A are self explanatory. "Not tested" is more a temporary note - if its still in the test after finishing, then the summary should explain why the feature was not tested. Remove this note in the final report


Minor Bugs

  • Problem1

Summary