A Microsoft app for iOS and Android devices that enables authentication with two-factor verification, phone sign-in, and code generation
The behavior matches an automated protection/block on outbound sharing and/or outbound email from the Microsoft account. The block itself can’t be cleared locally; it must expire automatically or be removed by Microsoft after account review.
Based on the available information, only the following actions are supported:
- Confirm the account is fully validated
- Go to the Microsoft account reputation check page:
https://account.live.com/reputationcheckand complete all required verification steps. - Ensure the Microsoft account profile is complete and that the Terms of Use have been accepted, as described in the OneDrive sharing guidance.
- Go to the Microsoft account reputation check page:
- Wait for automated limits/blocks to reset
- OneDrive and Outlook.com sharing limits and some blocks are time-based and reset after a period (commonly up to 24 hours) when triggered by high-volume or suspicious activity.
- If the block was triggered by repeated link sending, it may take longer, but the documented behavior is that limits and some blocks are temporary and automatically removed.
- Use direct links instead of OneDrive-generated emails (once the block is cleared)
- When the block is no longer active, upload the file to OneDrive, select it, choose Get link, and paste that link into a regular email message from the mail client. This avoids Outlook attachment blocking and uses OneDrive as recommended for potentially blocked file types.
- If the account itself is blocked or marked unavailable
- If any message such as “Your account is currently unavailable” appears when accessing OneDrive, follow the Microsoft services account reset process at the Microsoft services account reset page and complete the on-screen steps to reactivate the account.
If the backend spam/abuse block does not clear after the documented reset periods and after completing reputation and profile validation, the only remaining path is continued escalation with Microsoft support, as removal of such a backend block is not something that can be done from the client side.
References: