In some cases, the meeting room address found on this page might return a "Not found" error. This can happen for a couple of reasons:
- Most Common: The connected service account doesn't have impersonation access.
- You've changed the name of the room since creating it or have a hybrid Exchange/Office 365 configuration.
- Before stepping through this guide, make sure you've tried removing and reconnecting the O365 account via Settings > Integrations to confirm the issue persists.
Heads up: You may need the help of an administrator to complete this step.
If you connected to Office 365 account through a service account, confirm the service account has impersonation access to the room mailboxes. Remember that impersonation is different from "Full Access" delegation, and generally requires some configuration.
Here's how to set up impersonation for your service account.
How to find the alternate address
You can find an alternative room address from the user page. Generally it will follow the format of "room@YOURDOMAIN.onmicrosoft.com". Enter that address instead, and the room should go connect without issue.
Check the UserPrincipalName
If you still have a conflict, make sure the email you're providing matches the room's UserPrincipalName (UPN) inside of Office 365. When you create a new meeting room, the UserPrincipalName and mailbox address are the same by default, but they can change if you update email addresses. When in doubt, use the UPN with Robin.
If you're not sure about the UPN (or need to update it) you'll find these shell cmdlets handy:
Search by name or email
Get-MsolUser -SearchString "Conference Room"
Search by UPN
Get-MsolUser -UserPrincipalName email@example.com
Change a UPN
Set-MsolUserPrincipalName -UserPrincipalName [CurrentUPN] -NewUserPrincipalName [NewUPN]
More examples and documentation are available on MSDN: