How to Fix Microsoft 365 Shared Mailbox Error Code 530035
Question details
Users are unable to access a Microsoft 365 shared mailbox from specific geographic locations due to an authentication blockage.

- Product
- Microsoft 365
- Device & OS
- not provided
- Scenario
- A team is attempting to access a shared mailbox from different countries, but users in a specific region are blocked by security policies.
- Observed behavior
- The system throws Error Code 530035, preventing mailbox access for certain users while colleagues in other countries can connect successfully.
Ensure you have global administrator or security administrator privileges in Microsoft 365, as resolving this issue requires modifying Entra ID Conditional Access and location policies.
Review and Update Conditional Access Location Policies
Error 530035 is typically triggered by Conditional Access policies blocking sign-ins from unrecognized or restricted geographic locations.
Microsoft 365 restricts access based on IP address and country to prevent unauthorized logins. If a user travels or works remotely from a new country, the administrator must whitelist that region in the organization's Named Locations.
Sign in to the Microsoft 365 Admin Center, click 'Show all' in the left pane, and select 'Identity' or 'Azure Active Directory' to open the Microsoft Entra admin center.
Go to 'Protection' > 'Conditional Access' and select 'Named locations' from the sidebar.
Review your existing location policies. Add the affected user's country (e.g., Turkey) or specific IP ranges to the allowed list, then click 'Save'.
Go to 'Policies' under Conditional Access, locate any active block policies for international logins, and ensure the newly added location is excluded from the block list.

Configure Delegate Access Instead of Direct Login
Directly logging into a shared mailbox complicates MFA (Multi-Factor Authentication), especially across borders. Assigning delegate access bypasses this issue.
Open a Support Request with Microsoft
If Conditional Access policies are correct but the error persists, Microsoft Support must analyze the backend authentication logs.
Need a simpler office suite? Try WPS Office
Managing complex Microsoft 365 admin policies, Conditional Access rules, and MFA errors can be overwhelming. If your team needs a straightforward, reliable desktop office suite that doesn't rely on strict cloud authentication policies, WPS Office is an excellent free alternative.
- 1. Download the Installer: Visit the official WPS Office website and download the free installation package for your operating system.
- 2. Install the Software: Run the installer and follow the on-screen prompts to set up WPS Office on your computer.
- 3. Open Your Documents: Launch WPS Office to easily open, edit, and save your existing Microsoft Office files without compatibility issues.

Frequently Asked Questions
What exactly does Microsoft 365 Error Code 530035 mean?
Error Code 530035 indicates that a user's sign-in attempt was blocked by the organization's Conditional Access policies. This typically happens when logging in from an IP address or geographic location that the administrator has not explicitly approved.
Can multiple team members use different MFA methods for one shared mailbox?
Directly logging into a shared mailbox with different MFA methods is not supported and highly problematic. Best practice dictates assigning 'Delegate Access' to individual users, allowing them to access the shared mailbox using their personal accounts and personal MFA settings.
Why does the shared mailbox work for colleagues in Germany but not in Turkey?
This happens when your company's Azure AD (Entra ID) location policies explicitly trust logins from Germany but either flag logins from Turkey as a 'sign-in risk' or completely block them via Conditional Access rules.
Can I fix Error 530035 without an Entra ID Premium subscription?
If you do not have Entra ID Premium (which enables Conditional Access), the block might be caused by 'Security Defaults'. An administrator will need to disable Security Defaults or adjust basic MFA settings in the Microsoft 365 admin center to resolve the issue.




