SKUs: Velocity platform, AT-VGW-250, AT-VGW-HW-3, AT-VGW-HW-10, AT-VGW-HW-20, AT-VGW-SW, AT-VTPG-1000VL
Summary: When setting up scheduling with o365 and Oauth, you are prompted with "EWS could not log in using EWS credentials provided." This article will help you troubleshoot common issues and provide best practices for setting up your O365 integration.
Quick Navigation
Pre-requisites π
- Follow the Microsoft Room Scheduling PDF step by step
- Find it on any Velocity SKU resource page or use the link below
- Integration Note for Microsoft Room Scheduling - Pages 6-8 cover OAuth setup
- Velocity gateway needs internet access (green globe in top left)
- Admin rights in Velocity
- Admin rights in O365
- Important: Client secret expires after 2 years - set a reminder at 1 year 11 months to create a new one
What the Error Means π
Microsoft only tells us if everything works or doesn't - one incorrect setting triggers this error. Here's what to check:
Quick Checklist:
- Client Secret: Check if expired (2-year limit)
- Admin Email: Must match Azure exactly
- Manifest: Verify correct format
- API Permissions: Look for green checkmark
- Resource Mailbox: Confirm delegation setup
- Internet Access: Check for green globe
Admin Email Setup π§
Use the same email that created your Azure account - this email created the secret value and needs matching credentials.
Common Mistakes:
- Using a different email than your Azure registration
- Using a personal email instead of admin account
- Mixing up admin email with resource room email
Manifest Configuration π
The manifest setup is critical - one missing character can cause issues. Follow these steps carefully:
Setup Tips:
- Copy Exactly: Use the format below - no changes
- Check Carefully: All brackets { } and commas must be present
- Keep Original: Don't change any IDs or values
- Adding Content: If content exists, add comma after last }
"requiredResourceAccess": [
{
"resourceAppId": "00000002-0000-0ff1-ce00-000000000000",
"resourceAccess": [
{
"id": "dc890d15-9560-4a4c-9b7f-a736ec74ec40",
"type": "Role"
}
]
},
{
"resourceAppId": "00000003-0000-0000-c000-000000000000",
"resourceAccess": [
{
"id": "e1fe6dd8-ba31-4d61-89e7-88639da4683d",
"type": "Scope"
}
]
}
],
API Permissions π
After manifest setup, an admin must grant permissions. Look for the green checkmark to confirm success.
Key Points:
- Admin Required: Only admins can grant permissions
- Be Patient: Changes take a few minutes to apply
- No Checkmark? Try refreshing your browser
- Still No Access? Log in or contact your Azure Admin
Resource Room Delegation π’
Start with a test room - group policies can affect access. Microsoft offers several delegation methods.
Setup Steps:
- Test First: Create new room without permissions
- Be Patient: Wait 10-15 minutes after changes
- Double Check: Verify in both Exchange Admin Center and Azure Portal
- Access Rights: Admin needs full mailbox access
- Configuration: Confirm room mailbox settings
Troubleshooting π§
Common Issues and Solutions
Issue | Solution |
---|---|
EWS Login Error |
|
No Green Checkmark |
|
Resource Access Issues |
|
Need More Help? π
Before Contacting Support
Have these details ready:
- Version: Your Velocity firmware
- Error: Exact message text
- Progress: Steps completed so far
- Azure: Any portal error messages
Helpful Resources
Wrapping Up π¬
O365 integration is straightforward when you follow these steps carefully. Key points to remember:
- Watch your client secret expiration
- Double-check manifest formatting
- Verify permissions show green checkmarks
- Test with a clean room first