Article ID: 115140, created on Nov 15, 2012, last review on Mar 17, 2016

  • Applies to:
  • Operations Automation


POA cannot execute a task related to Office 365 service provisioning; the task fails with some confusing error message from the Microsoft API servers.

Office 365 APS application 2.2 or later is installed in POA.

The problem has to be investigated with the help of the Microsoft Support Team. The Microsoft Support Team needs the exact request and response XML packets which the MOSI Gateway Server (Microsoft Online Services Interface) uses to provision services in Microsoft Office 365 Cloud.

The article describes how to extract the request and response XML packets to/from the Microsoft Office 365 API servers on a POA-managed MOSI Gateway Server.


Starting from the Office 365 2.2 the following features were implemented in part of MOSI Gateway logging:

  • Logging of XML payload of MOSI requests/responses is enabled by default.
  • XML payload of calls to the Microsoft cloud is logged separately for each Office 365 customer.
  • XML payload of callbacks from the Microsoft cloud is logged to the separate file which is rotated daily.
  • If a call to the Microsoft cloud is failed the XML request and response are shown in the appropriate task log in POA.

The MOSI Gateway log files containing XML payload of requests and responses are placed in the MOSI_GATEWAY_HOME\App_Data\XMLPayload folder, where MOSI_GATEWAY_HOME is the directory where MOSI Gateway is installed, see Knowledgebase article #114674 for instructions how to find the needed folder.

There are the following log files:

  • Customer-CustomerId, where CustomerId is a globally unique identifier (GUID) of a customer in the Microsoft Office 365 cloud. These log files contain XML data of calls to the Microsoft cloud per customer.
  • Callbacks - this log file contains XML data of callbacks from the Microsoft cloud to the Office 365 Gateway for the current day (it is rotated daily).
  • CallbacksYYYYMMDD - these log file contain XML data of callbacks from the Microsoft cloud to the Office 365 Gateway for the past days.

So, having Office 365 customer ID Provider may easily find all XML requests/responses to/from Microsoft cloud in the MOSI_GATEWAY_HOME\App_Data\XMLPayload\Customer-CustomerID file using timestamp which is stored in the log file along with the XML payload like in the example below:

2012-10-09 09:55:37,512 INFO Request: <s:Envelope xmlns:a="" xmlns:s="">
<a:Action s:mustUnderstand="1"></a:Action>
<ActivityId CorrelationId="1a284d57-0c03-4e84-952d-e39848f27b4d" xmlns="">9d7d8afc-d1a3-4da5-b9e3-9453da839f17</ActivityId>
<CreateCustomerAccount xmlns="">
  <request xmlns:d4p1="" xmlns:i="">
        <d4p1:Line1>Rodeo Drive</d4p1:Line1>
        <d4p1:Line2 />
        <d4p1:State />
      <d4p1:BusinessName>Customer LTD</d4p1:BusinessName>
      <d4p1:CommunicationCulture i:nil="true" />
      <d4p1:CommunicationLanguage i:nil="true" />

Note: do not send the entire content of the XML packets; not all of this information is needed by the Microsoft Support Team for proper problem investigation. Send only the contents of the Header and Body tags.

Search Words

MOSI Callbacks location

MOSI Request and Response XML

MOSI Request and Response XML (Office 365 2.2 and later)


caea8340e2d186a540518d08602aa065 5356b422f65bdad1c3e9edca5d74a1ae e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF