Start with a short session
Open Connections → Microsoft Teams → Connect and sign in to your work account. Choose Set hours after connecting. A new schedule starts paused; start a timed session before enabling recurring hours.
Check availability from a separate account while the connected account’s Teams clients are closed. Provider observations and the status visible to other people are separate checks.
Teams decides the final status
Teams combines presence from different sessions. A preferred status or a Busy or Do not disturb session can take priority over Available. Allow time for updates to reach other clients.
Choose hours when you want to be reachable, and use Stop when that changes. Scheduling an availability request does not mean every Teams state becomes green.
Cloud early access and organization approval
The cloud connection uses Microsoft sign-in and delegated availability permissions. It manages the connected account’s presence session without access to chat messages or files.
Your organization may require administrator approval. Once approved, each employee connects their own account. Cloud availability requires an active OnlineHours trial or plan and a running server. Early-access validation is ongoing; checkout opens only for eligible connections.
Common questions
Can OnlineHours keep Teams green with my laptop closed?
The cloud connection can renew availability while your Teams clients and laptop are closed, provided the OnlineHours server stays running. Our current pilot uses a Mac as that server. A local browser-extension session still needs an awake computer.
Does the cloud connection work with a personal Microsoft account?
Microsoft’s delegated setPresence API supports work and school accounts. Personal Microsoft accounts are not supported by that route.
Will Available replace a meeting or Do not disturb?
Not necessarily. Teams applies its own presence priorities, including preferred states and other active sessions.