A Microsoft file hosting and synchronization service.
Hi @Karan Bhatt,
I hope you are doing well.
Thank you for reaching out and for sharing those screenshots. They were very helpful in identifying the issue. After reviewing your configuration, I can confirm that your SharePoint and Entra ID sharing policies appear to be set correctly. The issue you are experiencing is caused by a recent change Microsoft has rolled out (referenced in Message Center post MC1243549), which retires SharePoint's own One-Time Passcode (OTP) authentication for external users and enforces all external sharing to go through Microsoft Entra B2B Invitation Manager. Previously, disabling EnableAzureB2BIntegration let SharePoint and OneDrive manage external sharing separately from Entra ID. Now, Entra B2B domain and cross-tenant policies fully control sharing, causing the error that the domain isn’t allowed due to Azure AD B2B restrictions.
To resolve the issue, please follow these steps:
Step 1: Sync Entra B2B policy to SharePoint using PowerShell
- Open SharePoint Online Management Shell and connect to your tenant.
- Run the following command to force SharePoint to pick up the latest Entra B2B collaboration settings: Set-SPOTenant -SyncAadB2BManagementPolicy $true
- This step is important because after the rollout, SharePoint may still reference stale policy data. Changes can take up to 24 hours to fully propagate.
Step 2: Verify cross-tenant access settings
- Navigate to Microsoft Entra admin center > External Identities > Cross-tenant access settings.
- Under Default settings, select the Inbound access tab and ensure that B2B collaboration is set to Allow.
- If not, select Edit inbound defaults, allow access under External users and groups, Application.
- Select Save.
- Under Organizational settings, check if the recipient's domain is explicitly listed. If it is, verify that inbound B2B collaboration is set to Allow for that domain.
Step 3: Verify guest invite settings
- Navigate to Microsoft Entra admin center > External Identities > External collaboration settings.
- Under Guest invite settings, ensure the option is not set to "No one in the organization can invite guest users including admins."
-
- I recommend setting it to at least: "Member users and users assigned to specific admin roles can invite guest users including guests with member permissions."
I hope this information is helpful. Please follow the steps above and let me know if it works for you. If not, we can continue working together to resolve the issue.
Thank you for your patience and understanding. If you have any questions or need additional assistance, please don’t hesitate to reach out so I can continue to support you. If you found the response useful, please consider marking it as accepted, as this may help other community members who are looking for similar guidance.
I look forward to continuing the conversation.
If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.