Your RM Unify establishment is federated to Microsoft® 365. On a network computer, you launch a desktop Office app that is not activated, e.g. Microsoft Word and are prompted to sign into Office. You click 'Sign in' and enter your email address but instead of being redirected to a new window with the RM Unify sign in page, you see a new window with the error message:

We can't connect you.
Looks like we can't connect to one of our services right now. Please try again later, or contact your helpdesk if the issue persists.
HTTP 404
sts.platform.rmunify.com

This can be caused by one of the following:

1. Delivery of an incorrectly configured Group Policy Object (GPO), usually an Internet and Email GPO.
2. Incorrect system proxy on the affected computer.

1. Temporarily remove/disable the GPO from the affected user.
2. Reset the user's profile to remove any existing settings.
3. Log on to the network computer as the user.
4. Launch an Office app and check if activation is successful.
5. If activation is not successful, repeat for each GPO.

1. Temporarily remove/disable the GPO from the affected user.
2. Log on to the network computer as the user.
3. Launch an Office app and check if activation is successful.
4. If activation is not successful, repeat for each GPO.

1. Open an elevated command prompt.
2. Enter netsh winhttp show proxy and make a note of the current setting.
3. Determine if the current setting is correct for your network. If it is not correct, do one of the following:
   • Set the system proxy to 'Direct access (no proxy server)', using the command netsh winhttp reset proxy
   • Set the system proxy to use the IE proxy, using the command: netsh winhttp set proxy source=ie
   • Set the system proxy manually, using the command: netsh winhttp set proxy <proxy>:<port>. For example, if the proxy is 'proxy.internal' on port 80, the command would be: netsh winhttp set proxy proxy.internal:80.
4. Test if you can now launch and activate your desktop Office app.
5. If it fails, revert the 'winhttp proxy' settings to their original value recorded in step 2 above.
6. If it works, consult your usual network support provider about making the change permanent. Changing the 'winhttp proxy' settings may adversely affect other apps that rely on it.