Microsoft Entra ID invitations fully blocked due to suspicious activity

Melissa Van de Velde 0 Reputation points
2026-11-19T15:49:54.9866667+00:00

We are receiving HTTP 403 Forbidden errors when calling the Microsoft Graph invitation API.

Error message: "Invitations are blocked for this directory due to suspicious activity. Please contact Microsoft support for help."

This is a legitimate production application sending expected invitations to external guest users.

We are currently inviting approximately 380 users and successfully sent around 90 invitations before the restriction was triggered. All further guest invitations are now blocked.

Could you please investigate and unblock the guest invitation capability for our tenant as soon as possible?

Additionally, we would appreciate clarification on the applicable invitation limits and whether these can be increased to prevent this from happening again.

Thank you for your assistance.

Microsoft Security | Microsoft Entra | Other

1 answer

Sort by: Newest
  1. AI answer

    2026-11-19T15:51:01.7166667+00:00

    The exact HTTP 403 response requires Microsoft Support to remove the tenant-level invitation block; it cannot be cleared through Graph retries, Entra roles, or tenant configuration changes. Matching cases were resolved only after Microsoft’s internal team unblocked the affected tenant.^1^

    Request the unblock

    1. Stop the invitation job temporarily. Repeated 403 retries will not remove this block.
    2. In the Microsoft Entra admin center, open Help & support → New support request. If an Azure support plan is associated with the workforce tenant, use the technical support-request option documented by Microsoft.^2^
    3. Classify the request under Microsoft Entra ID / External Identities / B2B collaboration, and include:
      • The exact message: “Invitations are blocked for this directory due to suspicious activity. Please contact Microsoft support for help.”
      • UTC time of the first failure.
      • HTTP status (403), Graph request ID, client-request ID, and response body.
      • Tenant ID and affected application ID—only in the private support request, not publicly.
      • Approximately 380 intended invitations and approximately 90 successful invitations.
      • Confirmation that these are expected production invitations to legitimate external users.
      • Whether portal-created invitations fail as well as POST /invitations.
      • A request for backend review and removal of the directory-level invitation restriction.
    4. After Support confirms removal, send one test invitation. A successful Graph invitation returns 201 Created; only then resume the remaining workload.^3^

    A closely matching case—portal and Graph invitations blocked tenant-wide with this exact suspicious-activity message—states that no administrator-side configuration change clears the condition and that backend intervention is required.^4^

    Microsoft Q&A cannot investigate or modify the tenant directly, so do not post tenant identifiers or request traces publicly.

    Applicable invitation limits

    Two separate limit types apply:

    1. Daily B2B invitation limits

    Microsoft publishes these limits:^5^

    Tenant condition Published limit
    Paid license, tenant age ≤30 days 200 invitations/day
    Paid license, tenant age >30 days Microsoft Entra service quotas
    No paid license, tenant age ≤30 days 10 invitations/day
    No paid license, tenant age >30 days 100 invitations/day

    Because about 90 invitations succeeded, check the tenant’s age and licensing before resuming. If it is an unlicensed tenant older than 30 days, the planned 380 invitations exceed the documented 100-per-day limit. The documentation does not publish a self-service control for increasing these B2B invitation limits; ask Support whether a quota change is available for the tenant’s license and migration scenario.

    2. Graph request-rate throttling

    The /invitations endpoint has a separate limit of 150 requests per five seconds per tenant across all applications.^6^

    Normal Graph throttling returns HTTP 429, generally with a Retry-After header. The client should wait for that interval and retry; when no header is supplied, use exponential backoff.^7^ Your 403 suspicious-activity response is not the normal 429 throttling response, so adding retry delays will not unblock the tenant.

    After recovery:

    • Enforce the applicable daily invitation allowance in the job.
    • Keep request bursts below the documented /invitations rate.
    • Retry only 429 and transient server failures; do not automatically retry this 403.
    • Persist successful invitees so restarting the job does not resend completed invitations.
    • For future one-time migrations, open a support request beforehand to discuss case-specific mitigations; Microsoft recommends support planning where stricter security-related limits may apply.^8^

    References

    1. Microsoft Entra - Invitations are blocked - Microsoft Q&A
    2. Support and help options for Microsoft identity platform developers - Microsoft identity platform | Microsoft Learn
    3. Create invitation - Microsoft Graph v1.0 | Microsoft Learn
    4. Unable to send B2B guest invitations from Microsoft Entra - Microsoft Q&A
    5. Microsoft Entra service limits and restrictions
    6. Microsoft Graph service-specific throttling limits
    7. Microsoft Graph throttling guidance - Microsoft Graph | Microsoft Learn
    8. Microsoft Entra External ID deployment guide for tenant design
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.