A cloud-based identity and access management service for securing user authentication and resource access
This behaviour indicates that Microsoft Entra ID has placed a security restriction on your tenant due to automated abuse detection signals. The message suspicious behaviour is generated by Microsoft internal risk engines and is not based purely on visible audit log activity.
Tenant invitation blocking typically occurs when one or more of the following patterns are detected:
• High volume of external invitations in a short period
• Repeated failed invitation attempts
• Invitations to disposable or high risk domains
• Suspicious sign in activity linked to inviter accounts
• Newly created tenant exhibiting automation behaviour
The number of users in the tenant is not a determining factor. Even a tenant with fewer than one hundred users can be restricted if risk signals are triggered.
Important clarification
This restriction cannot be removed from the Azure portal. There is no administrative toggle to unblock invitations once the tenant has been flagged.
Recommended validation steps
Step 1 Check whether Azure AD B2B collaboration is correctly configured.
Navigate to:
Microsoft Entra admin centre External Identities External collaboration settings
Ensure that guest invitations are allowed for your user role.
Step 2 Review Microsoft Entra audit logs.
Go to:
Microsoft Entra admin centre Monitoring Audit logs
Filter for Activity category Invitation. Confirm whether failures show additional error codes beyond suspicious behaviour.
Step 3 Check Microsoft Entra sign in logs for the accounts sending invitations. Look for risk detections or identity protection alerts.
Resolution path
If the restriction persists and no configuration issue is identified, you must open a Microsoft support request. This is the only supported method to lift an automated tenant level invitation block.
When opening the case:
Select Microsoft Entra ID Choose B2B or External Identities Describe that tenant invitations are blocked due to suspicious behaviour
Microsoft support will review internal telemetry and determine whether the restriction can be removed. In most cases, once manual review confirms legitimate usage, the block is lifted.
Preventive recommendations after unblock
• Avoid bulk invitation scripts without throttling
• Ensure inviter accounts use strong authentication with MFA
• Limit invitation rights to specific roles
• Avoid inviting large batches of external users from high risk domains
Summary
This is not a configuration issue in your tenant. It is a security based enforcement triggered by Microsoft automated protection systems. The only remediation is a formal support request for tenant review and unblock.
If you can share whether invitations were automated or performed manually, further preventative guidance can be provided.