Why idle sign-out matters on forecast calls
Microsoft 365 signs out idle users of its browser-based web apps after an admin-set period, while Okta's documented session timer governs its Admin Console. A forecast call has a rhythm that most revenue leaders know well. Someone shares the workbook on screen, the room walks through the commit column, and then the conversation stalls while two people argue about a single close date. A few minutes can pass with nobody touching the keyboard. When someone finally clicks back into the shared file, the session may have ended. The result can be a sign-in prompt in the middle of a pipeline review or, worse, a few lost edits that somebody has to rebuild from memory.
Sign-out timers are the rules that decide how long a session can sit idle before the system asks for a sign-in again. Two sources of these rules come up often in revenue teams. The first is Microsoft 365, where many people open forecast workbooks, deal trackers, and slide decks in a browser. The second is Okta, the identity platform many companies use to control who can sign in to which apps. The two work differently, and the difference matters more than most people expect.
This post compares them in plain words. It is not a security review, and it does not tell you what your company's settings should be. Treat it as a guide to asking better questions before the next forecast call.
Key takeaways
- Microsoft's idle session timeout covers browser-based Microsoft 365 web apps, not desktop and mobile apps.
- Ask an administrator to confirm the setting under Org Settings in the Microsoft 365 admin center.
- Microsoft's inactivity test counts all web app tabs together, so one quiet tab alone may not sign you out.
- Okta's documented session settings cover the Admin Console, so confirm which rules apply to your team's apps.
- Save often, and respond as soon as the "Your session is about to expire" window appears.
The two timers at a glance
Microsoft 365 and Okta both use the idea of "idle" time, but they sit in different places in your technology stack. Microsoft's setting governs how long people can be inactive in Microsoft 365 web apps before they are signed out. Okta's documented setting governs sessions in its Admin Console, with a related field for app session idle time in the same section.
That gap is the most important thing to understand. A revenue leader who opens a forecast in a browser tab and a revenue leader who signs in to a CRM through Okta are usually dealing with two separate systems. A setting in one place will not necessarily change behavior in the other.
How Microsoft 365 idle session timeout works
Microsoft calls its feature idle session timeout. The Microsoft 365 admin documentation describes it this way: "Use idle session timeout to configure a policy on how long users are inactive in your organization before they're signed out of Microsoft 365 web apps." You can read the full page at Idle session timeout for Microsoft 365.
Two phrases in that sentence do most of the work. The first is "in your organization". The policy is set for your whole company, or at least for the Microsoft 365 tenant your account belongs to. You do not choose it for yourself in your own profile. The second is "web apps".
The same documentation sets a clear limit on the policy. Microsoft says: "Idle session timeout doesn't affect your Microsoft 365 desktop and mobile apps." That is a meaningful boundary. If a sales operations analyst keeps the forecast open in the installed Excel app on a laptop, the browser-based timeout does not apply to that copy, even though the same file might also be open in a browser tab. When people say "Microsoft logged me out," it helps to know which app they were using at the time.
Where administrators find the setting
The setting is not hidden, but it lives in the admin center rather than in any user's settings. Microsoft's instructions read: "In the Microsoft 365 admin center, select Org Settings -> Security & privacy tab and select Idle session timeout." The steps are in the same Microsoft documentation.
For a revenue leader, the practical takeaway is simple. You will usually not change this yourself. You will need a Microsoft 365 administrator to confirm the current configuration, and it is best to ask for that in writing before a quarter-end forecast cycle rather than during the call itself.
There is also a catch for organizations that already had older settings in place. The documentation says: "If you set up idle session timeout policies for Outlook web app and SharePoint, turning on idle session timeout in the Microsoft 365 admin center overrides the Outlook web app and SharePoint settings." In other words, a newer organization-wide setting can take precedence over app-specific settings that someone configured earlier. If your team recalls a SharePoint timeout that was set up earlier, do not assume it still controls the forecast file. Ask which setting is actually in effect.
What the warning looks like
Before a full sign-out, the browser-based experience gives people a chance to respond. Microsoft says: "When a user is inactive in Microsoft 365 web apps for the time period you chose, they see a Your session is about to expire window." The same page describes this behavior.
That warning is the moment to act. Read it, and decide what matters most in the next few seconds. If you have unsaved edits to a forecast cell or a note from the deal review, save first.
The warning matters most on calls where one person drives the screen and others only watch. The window appears to each user who is inactive for the chosen period, so everyone on the call should watch for it on their own screen.
Shared files and individual activity
The Microsoft rule is written about users: they must be inactive for the configured period, so the inactivity test applies to each person's own activity. A colleague's quiet screen does not tell you anything about your own activity.
This matters when a shared workbook is open on several laptops in the same room. One presenter may keep the screen moving while other people sit quietly. Only the sessions that meet the inactivity rule are affected, so the people who look idle are not automatically the ones who will be signed out.
The practical lesson is to stop trusting the screen. When a reviewer says "I'm still in the file," they may have been signed out without noticing. Ask them to check their own sign-in state, and to reopen the file if a prompt appears, before reading any figures out loud.
The all-tabs rule that changes call habits
The rule that catches many teams is stated plainly: "Users must be inactive on all Microsoft 365 web app tabs for the configured duration." The Microsoft documentation states the same condition.
This line has real consequences for forecast calls. Imagine a presenter who has the forecast workbook open in one Microsoft 365 web app tab and a deck open in a second. A quiet tab alone does not trigger a sign-out, because the condition covers every tab at once.
The opposite is also true. Because the condition covers all tabs together, it is hard to predict from the screen exactly when a sign-out will happen. Plan for the warning rather than for a precise moment. Keep the main forecast in one tab, avoid leaving unsaved changes in spare tabs, and remember that the timer is a backstop, not a schedule.
Okta: a different kind of timer
Okta is an identity platform. Its documentation on session lifetime is written for administrators working in the Okta Admin Console, and that distinction matters.
The steps for finding the setting read: "On the Sign On tab, click Edit in the Okta Admin Console session section." The source is Configure Admin Console session lifetime on Okta's help site.
Read the title again. The page is about Admin Console session lifetime, which, as the title suggests, is the session of the administrator who manages Okta itself. It is not automatically the session of a sales rep who opens a forecast app through Okta. The same section mentions a field for "Maximum app session idle time," and the instructions say you can "Set the Maximum app session idle time in hours or minutes." The same Okta page includes both points. Because that label appears in the Admin Console section, read the exact wording in your own tenant before assuming it applies to every app your team uses. For related checks, see Okta admin console session timeout checks.
How Okta's idle and lifetime settings relate
The Okta documentation draws one clear relationship between two values. It says: "The maximum session lifetime must be equal to or greater than the configured idle time." The Okta page states this rule in its configuration section.
In plain terms, the idle time is how long a session can sit still. The maximum session lifetime is the length the session is allowed to last overall. The lifetime value cannot be shorter than the idle value, so the documented rule rules out that pairing. If you ever see the two values configured in an odd way, that is a question for the administrator, and the rule gives you a concrete thing to check.
The page also explains how the idle clock moves. It says: "The idle expiration time resets based on your interactions within the Admin Console." In other words, activity inside the console restarts the idle countdown. For most revenue leaders this detail matters less than it does for the administrators who manage the console during a rollout or an audit.
Side-by-side comparison
Here is how the two timers compare:
- Where the setting lives. Microsoft: Org Settings, then the Security & privacy tab, in the Microsoft 365 admin center (source). Okta: the Sign On tab, in the Okta Admin Console session section (source).
- What it covers. Microsoft: Microsoft 365 web apps. Desktop and mobile apps are not affected (source). Okta: the Admin Console session, plus the maximum app session idle time field in that section (source).
- What counts as activity. Microsoft: users must be inactive on all web app tabs (source). Okta: the idle expiration time resets based on interactions within the Admin Console (source).
- Warning before sign-out. Microsoft: users see a "Your session is about to expire" window (source). Do not assume Okta shows a warning before sign-out.
- Relationship between values. Microsoft: no comparable rule is listed here. Okta: the maximum session lifetime must be equal to or greater than the configured idle time (source).
- Overrides. Microsoft: turning on idle session timeout in the admin center overrides older Outlook web app and SharePoint settings (source). Okta: no override rule is listed here.
Illustrative example: a forecast call, step by step
Imagine a regional forecast call that starts with the sales operations lead sharing a browser-based workbook. Then the call moves to a deal review, and the lead switches to a deck in a second Microsoft 365 web app tab.
Next, the lead stops typing to discuss a large deal. The workbook sits in one tab and the deck in another, and neither is touched. Now the all-tabs rule matters. A sign-out depends on whether every Microsoft 365 web app tab has been inactive for the configured period. The lead should read any warning, save pending changes, and respond before the session ends.
Suppose the warning is missed. Later, a manager asks about a figure that was typed earlier. The lead returns and finds a sign-in prompt. The fix is quick: sign in again, reopen the file, and confirm that the latest changes are present before reading any numbers aloud.
Common mistakes to avoid
- Assuming a desktop app follows the browser timer. The Microsoft documentation says idle session timeout does not affect desktop and mobile apps.
- Assuming the Okta Admin Console page covers every app your team opens. The page is about Admin Console sessions and the app idle field in that section.
- Assuming a quiet tab will trigger a sign-out. The Microsoft rule requires inactivity across all web app tabs.
- Ignoring the warning window. A few seconds of attention can save unsaved edits.
- Assuming an older SharePoint timeout still controls the forecast. A newer admin center setting may override it.
- Reading out numbers right after a sign-in prompt. Reopen the file and check the latest values first.
- Assuming the administrator knows which tools your team uses. Name the specific tools when you ask.
A checklist before your next forecast call
- Know where the file lives. If it is open in a browser, the Microsoft 365 web app rules apply. If it is open in a desktop app, they do not.
- Confirm the current Microsoft 365 idle session timeout setting with your administrator, and ask whether any older SharePoint or Outlook web app timeouts still apply.
- For Okta-managed apps, ask which session rules affect the apps your team uses for end users. Do not assume the Admin Console page answers that question.
- Save before stepping away from the screen, and save before any long pause in the call.
- When the "Your session is about to expire" window appears, read it and respond right away.
- If a sign-in prompt appears mid-review, sign in, reopen the file, and confirm the most recent edits are there before continuing.
- Give the shared screen to one presenter at a time, so someone is always watching for warnings. For more on sharing, see screen sharing checks for forecast calls.
Related guides: 3 password policy limits compared for Microsoft 365 and Okta · Microsoft 365 audit log retention: 5 rules to check.
Questions to bring to your IT administrator
- Is idle session timeout turned on in the Microsoft 365 admin center, and what configured period applies to our web apps?
- Does that setting override any older SharePoint or Outlook web app timeouts we still have?
- Which of our forecast tools run through Okta, and which session rules apply to them for end users?
- Does our Okta configuration include a maximum app session idle time, and where is it set?
- Are the settings the same for managers, sales reps, and finance users, or do different groups have different rules?
- If a session ends during a call, what should a user do first to avoid losing work?
Bring the list to the administrator in writing. Name the tools your team uses, the calls where the problem appeared, and the time of day when it happens. A specific question gets a specific answer, and that answer is what your team needs before the next forecast cycle.
The takeaway
The two timers protect different things and are configured in different places. Microsoft's setting is an organization-wide rule for browser-based Microsoft 365 apps, with a visible warning and a clear note that desktop and mobile apps are not affected. Okta's documented settings cover Admin Console sessions and an app idle field in the same section, with a rule that maximum lifetime cannot be shorter than idle time. Neither one tells you exactly how your next forecast call will behave on a given day.
The safest approach is practical. Know which app you are in, save often, respond to warnings, reopen the file after any sign-in, and ask your administrator before the call rather than during it. Those habits cost little, and they protect the one thing a forecast call cannot afford to lose: confidence in the numbers on the screen.
Your next step today: list the tools your team opens in a browser, and send that list to your administrator before the next call.
Frequently asked questions
Does the Microsoft 365 idle timeout apply to desktop apps?
No, idle session timeout doesn't affect your Microsoft 365 desktop and mobile apps.
Who sets the Microsoft 365 idle session timeout?
A Microsoft 365 administrator configures it in the Microsoft 365 admin center under Org Settings, on the Security & privacy tab.
Do Okta Admin Console session settings control every app my team uses?
Not necessarily: the Okta page covers Admin Console session lifetime, so confirm which rules apply to your apps.
What should I do if a sign-in prompt appears during a call?
Sign in, reopen the file, and check that the latest edits are there before reading any figures aloud.