'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Fix Microsoft 365 OfficeHome Error 530035 During Sign-In
Question details
The user is unable to sign into Microsoft 365 OfficeHome due to error code 530035 across multiple devices, requiring administrative investigation.
- Product
- Microsoft 365
- Device & OS
- not provided
- Scenario
- Attempting to sign into Microsoft 365 OfficeHome.
- Observed behavior
- The sign-in process fails with error 530035, blocking access to OfficeHome even on unregistered devices.
Ensure you have your Microsoft 365 account credentials handy and check your internet connection before attempting to troubleshoot the sign-in error.
Reset User Password and Submit a Service Request
A quick password reset might resolve temporary authentication glitches, but persistent 530035 errors usually require intervention from your Microsoft 365 administrator.
Error 530035 is often a tenant-level authentication issue. When standard diagnostics do not help and the error spans across multiple devices, deeper investigation via browser HAR logs and backend diagnostics is necessary.
Reset the Microsoft 365 password for the affected user account and attempt to sign in to OfficeHome again.
If the error continues, gather the request ID, correlation ID, timestamp, and application name displayed on the error screen.
Reach out to your organization's Microsoft 365 administrator with the collected details and any sign-in logs available.
Ask the administrator to open a formal service request in the Microsoft 365 admin center, providing the error code (530035) and browser HAR data if requested by Microsoft support.
Switch to WPS Office for a Hassle-Free Experience
If Microsoft 365 sign-in errors like 530035 are disrupting your workflow and you cannot wait for an administrator to resolve the tenant issue, consider using WPS Office. It provides a robust, free, and lightweight alternative that allows you to edit your documents offline without relying on complex cloud authentications.
- 1. Download and Install: Visit the official WPS Office website to download the free suite and follow the simple installation prompts.
- 2. Open Existing Documents: Launch WPS Office and directly open your existing .docx, .xlsx, or .pptx files seamlessly.
- 3. Work Offline or Online: Edit your documents locally without worrying about tenant-level sign-in errors or connectivity issues.
Frequently Asked Questions
What causes error code 530035 in Microsoft 365?
Error 530035 typically occurs due to tenant-level authentication issues, conditional access policy conflicts, or unregistered devices attempting to access OfficeHome. It usually requires backend investigation to fully resolve.
How can I collect HAR data for Microsoft support?
You can collect HAR (HTTP Archive) data by opening your browser's Developer Tools (usually by pressing F12), navigating to the Network tab, reproducing the sign-in error, and then right-clicking to export or save the network log as a HAR file.
Can I fix this error without an administrator?
If a simple password reset does not resolve the issue, you cannot fix it on your own. You will need your organization's Microsoft 365 administrator to investigate backend diagnostics and submit a service ticket to Microsoft.
