You only need to create a custom Logged Out Page if you’ve also turned on Force SSO for the default / custom login page. You can find this option under the separate Login Experience heading at the top of the same configuration page. If enabled, the option requires everyone, including visitors trying to reach the (default or custom) login page, to sign in with Microsoft first. If you have not turned that on, you can skip this whole section, because then users that log out or that were not able to sign in successfully with Microsoft will be sent to the (default or custom) login page.
When an error occurs during forced sign-in – for example Microsoft sign-in fails, an account has been deactivated – or someone simply signs out, WPO365 needs somewhere safe to send that user afterwards. This prevents users from being caught in a loop of being bounced straight back to Microsoft.
By default, WPO365 shows a simple, built-in page of its own for this (styled the same way as your custom login page, if you’ve set one up).
Only check the option to use a custom Logged Out Page, if you choose not to use the custom built-in Logged Out Page. With the option Use custom Logged Out Page left unchecked, WPO365 will use the built-in Logged Out Page and apply the branding that you configured in the section Customize branding Login / Logged Out Page.
Do nothing (recommended to start)
- Leave Use custom Logged Out Page unchecked. WPO365’s own built-in page will be used automatically, and you don’t need to configure anything else here.
To customize the Logged Out Page, please follow the steps explained in the Create a custom Login Route and hide wp-login.php.
Use a page of your own
- Check Use custom Logged Out Page.
- A Custom Logged Out Page URL field appears. Now enter the full web address of the WordPress page (or any page) you’d like people sent to instead, for example https://yoursite.com/signed-out/.
- If you later remove the address or uncheck this option again, WPO365 automatically falls back to its own built-in page, so there’s never a moment with nowhere to send someone.
- If your site uses a multi-lingual plugin (e.g. WPML) that adds a language “folder” to your web addresses (for example {your-website}/en/), that plugin may redirect visitors from the plain address you entered here to its language-specific version (e.g. {your-website}/en/signed-out/) — and WPO365 won’t recognize that redirected address as the same page, which can send visitors back to Microsoft to sign in again in a loop. If you notice this happening, add every language variant of your custom logged-out page’s address (e.g. both {your-website}/en/signed-out/ and {your-website}/nl/signed-out/) to the Pages freed from authentication list on the plugin’s Roles + Access configuration page.
- The same language-folder redirect can also leave a stray extra “/” at the very end of the web address (e.g. {your-website}/en/signed-out/?login_errors=LOGGED_OUT/). This is harmless in most cases, but if you’re using the shortcode on your own custom logged-out page to show a friendly message, that stray character can stop the message from being recognized. This comes from the multi-lingual plugin’s own redirect, not from WPO365 — adding the language variants above (which avoids that extra redirect hop entirely) prevents it too.
(Optional) Fine-tune the built-in page itself
These options only appear while you’re relying on WPO365’s own built-in page i.e. Use custom Logged Out Page above is unchecked. if you’re sending people to a page of your own instead, these don’t apply and are hidden.
- Check Hide title on the Logged Out page to leave off the Title text (set up in the branding section below) specifically on this page, while still showing it on your login page.
- Check Hide description on the Logged Out page to do the same for the Description text.
- A separate option, Show link to the site’s homepage, adds a small ← Go to {your site’s name} link to both this page and your custom login page.