Connection to Exchange Online Group Calendar

[J_Dobbo_D]

Hi,

I am successfully connecting to an Exchange Online Group Calendar in Power BI Desktop. The Group calendar's email address is xxx@abc.com and I am connecting with the credentials for yyy@abc.com who has permission to use the group calendar (as the group calendar has no password of its own, only permissions for those who can use it).

Power BI Desktop allows connection to the Group Calendar using this method and I can see all the data the calendar contains. But when I publish to the service, I am prompted to enter the Exchange credentials.

When I enter the same credentials as used in Power Bi Desktop (yyy@abc.com), the connection fails.

 If I try to add a new connection directly in the "Manage Gateways and Connections" screen of the Service, I get the following error.

 

"Currently, these cloud connections are not supported by Dataflows, Dataflows Gen2, and Datamarts. To create personal cloud connections for these experiences, please use the Dataflows or Datamarts editor in "Get Data"."

 

Also, the authentication method drop down box is blank.

In short, the Exchange connection works in Power Bi Desktop, but not in the Service. 

Does anyone know the solution or workaround, or is a data connection to a Group Calendar not possible? Many thanks.

[Anonymous · Accepted solution]

Hi @J_Dobbo_D 

Please try to reconfigure the data source in Power BI Desktop and select “OAuth2” as the authentication method when updating the data source credentials in Power BI Service.
1. Clear Exchange Online permissions in Power BI Desktop's data source settings.

2. Reconnect to Exchange Online, and select the “Microsoft account” method of connection.

3. Edit the data source credentials in Power BI Service, and select “OAuth2” as the authentication method.

4. Here is my final result, it works normally.

^{Best Regards,}

^{Jarvis Tang}

^{If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.}

[J_Dobbo_D]

Thank you so much. OAuth2 was the key!