Axcient Help Center

Integrating x360Sync with Microsoft 365 (Private Cloud)

If your organization has access to a commercial Microsoft 365 subscription, you can integrate x360Sync with Microsoft 365 apps, allowing users to edit files from within the web portal.

To configure this feature, SaaS partners can simply turn on the Microsoft 365 policy in the administrative web portal; however, if you are a Private Cloud partner, you must also request access to the Office Cloud Storage Partner Program so that you can deploy your own Microsoft 365 integration.

Note

This process can take a month or more to complete. Please plan accordingly.

Step 1: Request Access to the Microsoft Cloud Storage Partner Program

As a first step, you need to request access to the Microsoft Cloud Storage Partner Program.

  1. Navigate to the Office Cloud Storage Partner Program site and click the Join the Program button.

    PartnerProgram1.png
  2. Complete the registration form and click the Submit button when you are finished.This form will initiate the approval process. The approval process can take a week or more to complete.

    PartnerProgram2.png
  3. When you are approved for the program, Microsoft will contact you and provide access to the following resources:

    1. WOPI Yammer group—the WOPI Yammer group is the best way to submit requests, questions, or problems related to your Office Cloud Storage Partner Program membership.

    2. Web Integration Documentation—this WebHelp file outlines integration information and instructions.

    3. Shipping Information—this section of the WebHelp file provides instructions for validating and launching your completed web integration.

Step 2: Use the WOPI Protocol to Integrate Microsoft 365 with your Private Cloud Environment

After you are approved as an Office Cloud Storage Partner, you can use the WOPI protocol to integrate Microsoft 365 with your Private Cloud environment. This integration is already available in the x360Sync installation folder. You simply need to enable this feature through the configuration file (config.py):

  1. Open the config.py file.

  2. Update the following settings: WOPI_ENABLED = True WOPI_TESTING = True

Step 3: Validate your Integration

Before deploying to production, Microsoft must validate your integration package.

Note

Note: This process can take two weeks or longer. Before starting the launch process, please ensure that you have reviewed all requirements, and that you are ready to provide test accounts and videos.

To validate your integration:

  1. Before you begin the validation process, you must set up a test domain for Microsoft validation through Yammer. You can view an example Yammer request in the Yammer group.

  2. To prepare for the validation process, you have access to a WOPI Validation application that executes a test suite against a host’s WOPI implementation. The test suite verifies semantics for all the WOPI operations.

  3. Create test accounts and videos that will be used by Microsoft for validation during the release process. For a complete list of requirements, please reference Microsoft’s Web Integration Documentation.

  4. When you are ready, request Trello access through Yammer. You can view an example Yammer request for reference.

  5. When your request has been received, Microsoft will provide a private Trello board to track issues and promote communication between your team and Microsoft. Follow the provided Trello release guide (this will include setting up and providing an M365-specific subdomain for use by the WOPI protocol).

Step 4: Deploy to Production

When Microsoft has signed off on your integration, you can begin to roll out to your users.

Note

Microsoft might request that you roll out over a period of several days to ensure you do not overload Office for the web or your WOPI servers.