Adding a Rovo 3P One Drive connector can fail with a bad request

XMLWordPrintable

    • 2
    • Minor

      Issue Summary

      Adding a One Drive connector sometimes fails with an HTTP 400 bad Microsoft with a response like:

      {
          "message": "Configuration saved with errors",
          "data": "400 Bad Request from POST https://manage.office.com/api/v1.0/<UUID-REMOVED>/activity/feed/subscriptions/start"
      }

      It seems like this may be the result of a missing app permission not documented on this page: https://support.atlassian.com/organization-administration/docs/connect-onedrive-to-rovo/ 

      Steps to Reproduce

      1. Go through the steps for adding a OneDrive connector on https://support.atlassian.com/organization-administration/docs/connect-onedrive-to-rovo/
      2. Connector creation will fail on AdminHub with the above error

      Expected Results

      The OneDrive connector creation should go through successfully and start ingestion of data.

      Actual Results

      The below exception is thrown:

      { "message": "Configuration saved with errors", "data": "400 Bad Request from POST https://manage.office.com/api/v1.0/<UUID-REMOVED>/activity/feed/subscriptions/start" } 

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            Assignee:
            Zach Marszal
            Reporter:
            Hugh Wu
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: