Forum Discussion
Problem Sharing Power BI Report to One External Client - We are on Fabric Capacity Plan F64
- 1 year ago
Thanks again for the helpful replies.
Our client has responded with some information:
- Recent Activity: https://mysignins.microsoft.com
- they checked this and all the logins are OK, including the one to our tenant.
- Organisations page https://myaccount.microsoft.com/organizations
- This correctly shows our organisation as a collaboration organisation
- Risky Users report: https://portal.azure.com/#blade/Microsoft_AAD_IAM/SecurityMenuBlade/RiskyUsers
- The client doesn't have access to this
At this stage, this is pointing to our organisation's tenant flagging thier domain as "risky users".
We are waiting for our central IT group to confirm.
- Recent Activity: https://mysignins.microsoft.com
Thanks to everyone for their helpful replies.
The client eventually came back to use to let us know the error message they were getting.
"Your account is blocked. - We've detected suspicious activity on your account. Sorry the organization you are trying to access restricts at-risk users. Please contact your <client's orgiansation name> admin."
Not sure from this as to whether it is their org or our org that is doing the blocking. We've asked the client to check the following:
- Recent Activity: https://mysignins.microsoft.com
- see if their login is getting blocked and any info we can get off this
- Organisations page https://myaccount.microsoft.com/organizations
- This should show our organisation as a collaboration organisation
- Risky Users report: https://portal.azure.com/#blade/Microsoft_AAD_IAM/SecurityMenuBlade/RiskyUsers
- Hopefully we will see the users in this report and be able to clear them for access
We are also doing the same within our organisation. Hopefully this will point to where the client's users are getting blocked.
As a general comment Microsoft documentation that people have pointed us to - it's partially out of date.
With the introduction of Fabric and the F64 SKU capacity plan, you don't have to go down the full B2B sharing route. All you have to do is the ad-hoc sharing route as described in https://learn.microsoft.com/en-us/power-bi/enterprise/service-admin-azure-ad-b2b
Essentially, you are treating externals like they are an internal user and Fabric takes care of the rest.
Thanks again to veryone who replied. I'll update the post once we find out where the blocking was coming from.
- Huntly1 year agoNew Member
Thanks again for the helpful replies.
Our client has responded with some information:
- Recent Activity: https://mysignins.microsoft.com
- they checked this and all the logins are OK, including the one to our tenant.
- Organisations page https://myaccount.microsoft.com/organizations
- This correctly shows our organisation as a collaboration organisation
- Risky Users report: https://portal.azure.com/#blade/Microsoft_AAD_IAM/SecurityMenuBlade/RiskyUsers
- The client doesn't have access to this
At this stage, this is pointing to our organisation's tenant flagging thier domain as "risky users".
We are waiting for our central IT group to confirm.
- v-ssriganesh1 year ago
Community Support
Hello Huntly,
Could you please confirm if your query have been resolved? If they have, kindly mark the helpful response and accept it as the solution. This will assist other community members in resolving similar issues more efficiently.
Thank you.
- Recent Activity: https://mysignins.microsoft.com
- Anonymous1 year agoNot applicable
This link is dead (404). Can you explain more about treating "externals like they are internal" users?