Forum Discussion

happywilli's avatar
happywilli
New Member
9 years ago

Connect to Partner Center Analytics Preview

Failed to update data source credentials: The credentials provided for the Partner Center Analytics Connector source are invalid. (Source at PartnerCenterAnalytics.)Hide details

Activity ID:296b38f5-7d3a-4fad-b5aa-d4d7ef83e2cd
Request ID:45435de3-02dc-137a-a33f-1b18df90b3ab
Status code:400
Time:Mon Oct 30 2017 12:47:56 GMT+0100 (W. Europe Standard Time)
Version:13.0.2819.181
Cluster URI:https://wabi-north-europe-redirect.analysis.windows.net

 

Trying to connect our tenant but getting error message

5 Replies

  • v-qiuyu-msft's avatar
    v-qiuyu-msft
    Icon for Community Support rankCommunity Support

    Hi happywilli,

     

    I seen the same issue reported before,already send the email to consult this issue internally. Will update here once get any information. 

     

    Best Regards,
    Qiuyun Yu

  • v-qiuyu-msft's avatar
    v-qiuyu-msft
    Icon for Community Support rankCommunity Support

    Hi happywilli, 

     

     

    I got information that partner tenant id is required to analyze the issue. Would you please send it to me via private message? 

     

    Best Regards,
    Qiuyun Yu

    • v-qiuyu-msft's avatar
      v-qiuyu-msft
      Icon for Community Support rankCommunity Support

      Hi happywilli,

       

      Please check if you are partner tier 1. You can see this limitation here: 

       

      This version of the app is designed for direct partners (tier 1) in the Cloud Solution Provider program. You're a direct partner if you do business directly with Microsoft and with customers. To install the app, you must be a global admin, admin agent, or billing admin for your company’s account.

       

      Best Regards,
      Qiuyun Yu

      • mazakane's avatar
        mazakane
        New Member

        Hi, I do have the same issue, although we're CSP partner tier 1, can you pls. help? 

  • Zeeshan's avatar
    Zeeshan
    Frequent Visitor

     I am also facing the same error. Any update "How to solve this issue"?