Sometimes the meeting room address on the Microsoft 365 resource mailbox page returns a "Not found" error. This can happen for these reasons:
- Most Common: The connected service account does not have impersonation access.
- You changed the name of the room after you created it, or you have a hybrid Exchange/Microsoft 365 configuration.
Before you follow these steps, remove and reconnect the Microsoft 365 account in Settings > Integrations. This confirms that the issue is still there.
Enable impersonation
You may need help from an administrator for this step.
If you connected your Microsoft 365 account through a service account, confirm that the service account has impersonation access to the room mailboxes. Impersonation is different from "Full Access" delegation, and usually needs some configuration.
See set up impersonation for your service account.
Find the alternate address
You can find an alternate room address on the user page. It usually has the format "room@YOURDOMAIN.onmicrosoft.com". Enter that address instead, and the room should connect.
Check the UserPrincipalName
If you still have a conflict, make sure the email you enter matches the room's UserPrincipalName (UPN) in Microsoft 365. When you create a meeting room, the UserPrincipalName and mailbox address are the same by default. They can differ if you change email addresses. If you are not sure, use the UPN with Robin.
To check or change the UPN, use these shell cmdlets.
Search by name or email
Get-MsolUser -SearchString "Conference Room"
Search by UPN
Get-MsolUser -UserPrincipalName boardroom@domain.com
Change a UPN
Set-MsolUserPrincipalName -UserPrincipalName [CurrentUPN] -NewUserPrincipalName [NewUPN]
For more examples and documentation, see MSDN:
Hybrid environments with Microsoft 365
In most cases, it is easier to connect Robin with Microsoft 365 than with Exchange. If the room resources you want to manage are available to the Microsoft 365 tenant, you can skip the Exchange setup.