1. Review the status already selected
Open your Teams profile and inspect the current availability setting. Review any selected status duration and use the built-in reset control when you want to return to normal behaviour.
A duration setting is not a guarantee of a permanent green indicator. Your account can still be affected by the presence rules Teams applies.
2. Check the other sessions
Look at Teams on your phone, desktop and browser. A preferred state overrides session-level states; within those sessions, Do not disturb and Busy take priority over Available.
If you are in a call or have chosen a different status intentionally, account for that before judging a scheduling tool.
3. Try a bounded local session
In the free OnlineHours extension, select Teams, sign in through the dedicated tab and start a short timed session. Keep the browser and computer running.
Check the visible result from another permitted view. The extension is experimental, so begin with a short test rather than relying on an entire working day immediately.
4. Save hours only after the first test
Choose working days and an explicit time zone. Test the end of the window too: a useful routine must be understandable when you stop as well as when you start.
The planned cloud option uses the Microsoft Graph presence API for work and school accounts. It remains pending OAuth setup and live validation, so it cannot yet replace a running local browser.
Common questions
Can I guarantee that Teams always shows Available?
No. Other sessions, preferred states and Teams’ own rules can determine the final indicator.
Does the cloud API need access to my Teams messages?
The presence update uses delegated Presence.ReadWrite. That permission is for presence, not chat-message access.