Exchange Online OWA “500 Something went wrong. Repeating redirects detected”

Scenario: When attempting to access Outlook on the Web (OWA), you receive the following error:

Solution: This was a Microsoft issue. Their frontend servers within the Exchange Online environment were erroring out. In our case we were impacted well before the global Microsoft incident/advisory was issued (Ex231181). We did notice that it was the same frontend server being reported in the error details amongst all impacted clients, it just took a while for Microsoft to acknowledge the issue. I did see other articles suggesting it could be Microsoft Admin rights and roles assigned to the user, but in our case these were just normal users that were being impacted.


Open another Mailbox via Outlook Web App (OWA)

Scenario:  You have permission to another users mailbox and you want to open that mailbox via Outlook Web App (OWA)


  1. Sign in to your account in Outlook Web App.
  2. On the Outlook Web App nav bar, click on your name. A list appears.
  3. Click Open another mailbox.
  4. Type the alias or email address of the other mailbox that you want to open. Another Outlook Web App session opens in a separate window, allowing access to the other mailbox.

Send email from another Person or Group

Scenario: When sending an email, you want to Send as/Send on behalf as someone else.

Via OWA:  

1. Log in to your mailbox using Outlook Web App.
2. Click + New mail above the folder list. A new message form will appear in the reading pane.
3. Click the more options menu … , and then click Show from.
4. Select the email address that displays in the From field and delete it.
5. Type the name of the user for which you have permission to send email. If you don’t see the name in of the person you want to send From box, you can click Search contact & directory to search the directory of your organization.
6. Add recipients, a subject, and the contents of the message as you typically do, and then click send Send.

Via Outlook 2013/2010

1. Click on New Email.
2. Click the From box and select Other E-mail Address… from the dropdown. (The From field is hidden click Options from within the message and then select From.)
3. You will now be able to type in or select the email address you wish to send as/send on behalf as.

Recover Deleted items in Outlook or Outlook Web App

Recover deleted items in Outlook or Outlook Web App

Restore deleted items in Outlook 2013

Restore deleted items or email in Outlook Web App

Restore Deleted items in Outlook 2010


Configuring Message rules for a shared Mailbox

Configuring message rules for a shared mailbox

Scenario: How do I access a shared mailbox and change a rule.  I do have admin rights and full access to this mailbox but when I do a file > open> and try to change the rules, it reverts back to my primary mailbox rules.

Note: Exchange 2010 users cannot modify rules for mailboxes in Exchange 2013, and vice versa

There are several methods to get this to work:

Method 1: Outlook 2010 or Outlook 2013

Configuring Message rules for a shared Mailbox/Service Mailbox

If you are using Outlook 2010 or Outlook 2013 and either have been granted Full Access permissions to the mailbox or have been provided separate credentials for it, then you can also configure this shared mailbox as an additional Exchange account or add it as a secondary mailbox of your own.

How to add an additional mailbox in Outlook 2010:

How to add an additional mailbox in Outlook 2013

Once the mailbox has been added, select its Inbox folder and add the rule as you would normally do for your own mailbox.

Method 2: Outlook Web App

When you have been granted Full Access permissions, then you can log on with your own username and password and click on your own name in the top-right corner to get to the option of opening another mailbox.

If you haven’t been granted Full Access permissions but do have separate log on credentials for the additional mailbox, you can use that to log on.

Once logged in, you can create a message rule in the following way:

    For OWA 2013:
    Gears icon (right side of your name)-> Options-> Organize email

    For OWA 2010:
    Options (below your name)-> Create an Inbox Rule…

A user receives ‘Something went wrong Sorry, we can’t get that information right now. Please try again later. If the problem continues contact your helpdesk’ error message when accessing OWA.

Scenario:  A new mailbox is provisioned and the user is receiving the following error when accessing their mailbox via OWA:

😦something went wrong

Sorry, we can’t get that information right now. Please try again later. If the problem continues, contact your helpdesk.

All normal mail protocols such as OWA and ECP were enabled by default.

Resolution:  I performed a search against the email address for that mailbox and came across two mailboxes that had the same email address  (get-mailbox I removed this email alias from the user who was not using it.  The user experiencing the problem could now login to OWA.

OWA message saying “403 Sorry! Access denied” You don’t have permissions to open this page

Issue: User tries to go into the OWA and change the options, but got a message saying “403 Sorry! Access denied” You don’t have permissions to open this page. Wait 15 minutes and try again. Customer already has the correct default role assignment policy assigned.

Cause: Troubleshooting revealed that ecpenabled was set to false for this user under casmailbox

Resolution: From PowerShell command prompt, type Set-casmailbox -id testuser -ecpenabled $true

Emails in users “Inbox” are automatically moved to a folder (not created by user), labeled “Junk”


A new email arrives, it sits in the “Inbox” anywhere from a few seconds to a few minutes before it moves to a folder labeled “Junk”. This is not the default “Junk E-Mail” folder in Outlook/OWA.


Client has a Samsung Galaxy device configured to view users mailbox.


  1. Go into the E-Mail application on the Samsung Galaxy
  2. Press the Menu Key, select Settings, then General Settings
  3. Select Spam addresses and remove any addresses that should not be in there, such as your corporate domain.

Cant delete message in OWA.
Error: Access is denied.
Solution: Insure EWS is enabled on mailbox

In Exchange Powershell run
         get-casmailbox mailboxname |select ewsenabled
if       EwsEnabled                 : False

then enable by running the following command.
         set-casmailbox mailboxname -ewsenabled $true

X-OWA-Error: Microsoft.Exchange.Security.Authentication.TokenMungingException

Scenario:  When a user tries to access OWA, the receive the following error:

something went wrong
Sorry, we can’t get that information right now. Please try again later. If the problem continues, contact your helpdesk.

X-OWA-Error: Microsoft.Exchange.Security.Authentication.TokenMungingException

Resolution: This is the result of the mailbox being a ‘linked mailbox’ and having a value in the ‘linked master account’.

Run the following to view the value:
get-user batman15 | select linkedmasteraccount

Run the following to remove the value:
set-user batman15 -linkedmasteraccount $null