• Article for your preferred language does not exist. Below is international version of the article.

Article ID: 113800, created on May 2, 2012, last review on Aug 12, 2014

  • Applies to:
  • Operations Automation 5.x

Release Notes

Full release notes can be downloaded here.

Functional Changes

New settings are added for the Microsoft Office 365 Application.

Fixed Issues

APS-8408 Office 365 subscriptions are not disabled in the Microsoft cloud
APS-8044 If a subscription has expired, the configuration task which tries to deactivate this subscription fails


The Microsoft Office 365 Application Package can be downloaded here.


To install the Microsoft Office 365 Application, use the instructions provided in the PA Office 365 Integration Provider's Guide.

Upgrade Procedure

To upgrade the Microsoft Office 365 Application, perform the following steps:

1. Import the Microsoft Office 365 Application Package to Parallels Operations Automation (POA). See POA Provider's Guide >> Application Hosting > Managing Applications > Importing Application for details.
2. Upgrade the Office 365 Gateway:
    a. Put the Microsoft Office 365 Application Package on the Office 365 Gateway Host.
    b. Extract the MOSI-Gateway.zip file from the Microsoft Office 365 Application Package.
    c. Stop the Office 365 Gateway IIS WebSite and Application Pool.
    d. Place the content of the MOSI-Gateway.zip file over the existing Office 365 Gateway installation (confirm overwriting of existing files, except the web.config file). Refer to the Knowledgebase article http://kb.sp.parallels.com/en/114674 to find the folder where the Office 365 Gateway files are located.
    e. If the upgrade is performed from Office 365 Integration 2.2, replace the existing web.config file with the file from the MOSI-Gateway.zip file.
        Otherwise, modify the existing web.config file in the following way:
        Go to the <log4net …> section.
        After the AuditAppender appender, add the following appenders:

<appender name="XMLAppender" type="PatternFile.PatternFileAppender">
    <file value=".\\App_Data\\XMLPayload\\Customer-%property{CustomerId}"/>
    <appendToFile value="true"/>
    <lockingModel type="log4net.Appender.FileAppender+MinimalLock"/>
    <layout type="log4net.Layout.PatternLayout">
        <param name="ConversionPattern" value="%d %-2p %m%n"/>
<appender name="XMLAppenderCallback" type="log4net.Appender.RollingFileAppender">
    <file value=".\\App_Data\\XMLPayload\\Callbacks"/>
    <appendToFile value="true"/>
    <rollingStyle value="Date"/>
    <datePattern value="yyyyMMdd"/>
    <layout type="log4net.Layout.PatternLayout">
        <param name="ConversionPattern" value="%d %-2p %m%n"/>

    After the audit named logger, add the following named loggers:

<logger name="xml" additivity="false">
    <level value="INFO"/>
    <appender-ref ref="XMLAppender"/>
<logger name="xml-callbacks" additivity="false">
    <level value="INFO"/>
    <appender-ref ref="XMLAppenderCallback"/>

    f. Start the Office 365 Gateway IIS WebSite and Application Pool.
    Important: Do not rename or remove any files from the Office 365 Gateway installation.
3. Upgrade existing Microsoft Office 365 Application instances. See POA Provider's Guide >> Application Hosting > Bulk Application Upgrades for details.

caea8340e2d186a540518d08602aa065 2554725ed606193dd9bbce21365bed4e 5356b422f65bdad1c3e9edca5d74a1ae e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF