Managing external identities to enable secure access for partners, customers, and other non-employees
Hi Dvibe,
you will need to open a ticket, this site doesn't respond to support requests.
What to do:
• Open a support case as a Global Administrator: Microsoft 365 admin center > Support > Help & support (or Azure portal > Help + support > New support request > Microsoft Entra ID).
Title it "B2B invitations blocked for directory due to suspicious activity" and include the tenant ID, the exact Graph error text and code, request IDs and timestamps, and a short description of the legitimate onboarding (customer name, expected volume, domains). Support reviews the activity and removes the flag; turnaround is usually a few business days.
• While you wait, confirm the basics so nothing else is in the way:
Entra ID > External Identities > External collaboration settings (who can invite, allowed/blocked domains), and Cross-tenant access settings (inbound/outbound B2B collaboration for the partner tenants).
Changes there can take 15–60 minutes to apply.
Avoiding it next time:
• Throttle bulk invitations: send them in smaller batches spread over time rather than thousands in one run, and use a dedicated service principal with only the Guest Inviter role.
• Prefer email one-time-passcode / direct-link redemption (invitation email suppressed) or self-service sign-up user flows for large customer onboarding instead of mass invitation emails.
• Restrict Collaboration restrictions to an allow-list of known customer domains.
I hope that helps!