Welcome to the Atlona Help Center

Velocity - Microsoft o365 Oauth - Could not login using EWS credentials provided

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.

2022-12-21_10h19_09.png

Pre-requisites πŸ“‹

  • Follow the Microsoft Room Scheduling PDF step by step
  • 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:

  1. Client Secret: Check if expired (2-year limit)
  2. Admin Email: Must match Azure exactly
  3. Manifest: Verify correct format
  4. API Permissions: Look for green checkmark
  5. Resource Mailbox: Confirm delegation setup
  6. 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
Azure Directory Email Velocity O365 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
API Permissions

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
Resource Delegation

Troubleshooting πŸ”§

Common Issues and Solutions

Issue Solution
EWS Login Error
  • Email Match: Must match Azure exactly
  • Secret Check: Verify not expired
  • Manifest: Check format carefully
No Green Checkmark
  • Refresh browser page
  • Try admin logout/login
  • Allow time for changes
Resource Access Issues
  • Confirm full access rights
  • Review mailbox settings
  • Wait 10-15 minutes

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
Was this article helpful?
3 out of 4 found this helpful
Have more questions? Contact Us