Hello, I’m Nora, your AI guide from Technology Last Stop. This guide covers Connect Zoom user-type inventory. Read the user types returned for active, inactive and pending Zoom accounts. Current availability: Read adapter implemented; company authorization and successful live sync required.

Before you start. An authorized company administrator with Vendor licenses management permission and an approved provider data-use scope. The company’s protected integration vault. Use a dedicated provider application; never put credentials in a KB, video, chat or source file.

Step 1. Create and activate a dedicated Server-to-Server OAuth application in the company Zoom account. Grant user:read:list_users:admin.

Step 2. Enter the account ID, client ID and client secret in the Zoom form. Connect exchanges these credentials for an account token during synchronization.

Step 3. Save the encrypted connection in Companies > company > Vendor licenses. Choose Sync now in production after provider authorization. Dev and QA isolate external operations. Review the recorded sync result and compare the snapshot with the provider console.

Step 4. Review Basic, Licensed and any other user types returned by Zoom. Account state is shown separately from the user type; pending or inactive users are not silently relabeled active.

Step 5. Purchased capacity and unreturned add-on licenses remain unknown. A missing administrator role is explicitly marked unavailable instead of guessed.

Step 6. If a user moves between status lists during collection, the reader rejects that changing snapshot. Retry after the provider state settles.

Now verify the result. Compare user types and account states with Zoom. Confirm no user update, license assignment or meeting operation was requested. A successful company sync is required before describing the connection as healthy; an available adapter alone is not a connected account. Check a second company and a view-only account: neither can change this company’s credentials or lifecycle state. Pause, Resume and Trash affect only the local connection. Resume waits for a separate Sync action; no vendor user or license is modified.

If you get stuck. 401 or 403: check credential expiry, the selected provider organization and the exact required permissions. Do not grant broad write access merely to bypass a failed read. A failed or incomplete provider response preserves the last complete snapshot. Review the error, correct the connection and explicitly retry. On a 429 rate-limit response, wait for the provider’s retry window before another manual sync. Large inventories can require a separately designed scheduled export; the current bounded sync does not commit partial results.

Use the current written guide for exact URLs, permission names, and provider documentation. Pause before entering credentials, and keep them in protected configuration. I’m Nora, your TLS guide.