Read Microsoft 365 usage reports across the last 7, 30, 90 and 180 days before a new seller's check-in, allowing for reporting delays.
Key takeaways
- Note the date and time of each report pull, and the window you chose.
- Confirm that each report had time to become available before you rely on it.
- Use onboarding dates as context; read weeks separately only if a supported weekly breakdown is available.
- Check the start date against the 180-day window before you read it as history.
- Decide on one or two next steps, a date for the next pull, and who will own each step.
If your company uses Microsoft 365, the usage reports in the admin center can give that conversation a factual starting point. Microsoft explains: "Microsoft 365 admin center usage reports provide insight into how people in your organization use Microsoft 365 for business services." ( Microsoft Learn: usage reports overview)
Numbers from those reports support questions. They do not answer them. A quiet week can come from onboarding, a training session, travel, or work that happens in a tool you are not looking at. Treat each number as a prompt for a question you ask the seller directly, and keep a note of what they tell you so the next check-in can pick up where this one ends.
This post covers the four windows that Microsoft gives for its usage reports. The sections follow an order that suits a first check-in: the goal of the meeting, then timing, then the windows from shortest to longest, and finally how to combine them.
Set the goal of the check-in first
The goal of the first check-in is to agree on what good work looks like over the next few weeks, not to grade the first ones. A new seller is still learning the accounts, the tools, and the people they will work with. If the meeting opens with a list of low numbers, the seller may spend the conversation defending themselves instead of describing what they need.
Start by stating the purpose out loud. Tell the seller that you are looking at usage data together so you can understand how their first weeks went and what would help next. That framing turns the reports into shared material rather than evidence in a case. It also gives you a reason to ask the seller to explain each pattern in their own words.
Decide before the meeting what you want to leave with. A useful outcome is a short list: a few things the seller will try, one or two things you will change on your side, such as access or training, and a date for the next look at the data. If you leave with a list like that, the usage reports have done their job, even if some of the numbers were confusing. Use a sales coaching agenda to organise that conversation.
It also helps to agree on the tone before the first chart appears. Say that the data is a starting point, and that you expect the seller to add context you cannot see from the admin center. Sellers who hear that at the start are more likely to bring their own examples, and those examples usually explain the numbers better than any further analysis on your side.
Check the timing before you read the numbers
The reports typically become available within 24 to 72 hours, but might sometimes take several days to become available, according to Microsoft's usage reports overview. That gap matters for a new seller. If you pull a report on the day an account is set up, a short window may still be filling in, and a blank or low number may reflect reporting delay, though timing alone does not establish its cause.
Plan your pulls with that delay in mind. If you can, pull the reports a few days before the check-in rather than on the morning of it, so you have time to notice a gap and pull again. A report pulled the night before a meeting may leave too little time to investigate gaps, though another look may still be possible.
Write down the date and time of each pull and the window you chose. Put those details on any screenshot or export you bring to the meeting. When you and the seller look at the same numbers, you should both know which period they cover and how fresh they are. Without that note, a number that changes between two pulls looks like a change in the seller, when it may only be a change in the data.
If a number surprises you, check whether the report had time to become available before you raise it. Pulling the same window again later is a simple test. If the number moves toward what you expected, the first pull may have been too early. If it does not move, check freshness and completeness before interpreting it.
Keep your pull notes in one shared document, with a row for each pull showing the window, the time, and what you plan to ask. Anyone who reads the file later, including you at a future check-in, should be able to tell what was known on the day of the meeting.
The last 7 days
The last 7 days is the shortest of the four windows that Microsoft says its usage reports are generally available for. The overview says, "Usage reports are generally available for the last 7, 30, 90, and 180 days." ( Microsoft Learn: usage reports overview)
Use the 7-day view for questions about the current week, not for a verdict on the seller. One week is a small slice of anyone's work. Holidays, travel, training, or an account that was still being set up can all shape what that week looks like. If you see little activity, ask what the week held before you draw any conclusion.
A good first question is what the seller was working on that week. Ask which tools they opened first, what they were trying to finish, and whether anything blocked them. Blockers are easy to miss from the outside. A login that did not work, a file they could not open, or a meeting that ran long can all leave a thin week behind.
If the answer points to a setup issue, such as a missing permission or a sign-in problem, the report has done its job by prompting the question. Fix the issue, write it down, and move on. Keep a setup problem separate from any performance conversation, so the seller is not judged for something that was on your side to fix.
Check whether the week you are reading is the seller's first week or a later one. The first week may include setup, introductions, and walkthroughs, so a light count there may say more about the setup than about the work. Label it that way in your notes and avoid comparing it with later weeks.
Ask the seller for a one-sentence description of their week before you show them any chart. Their description gives you a frame for the numbers, and it keeps the first minutes of the meeting on their experience rather than on your screen.
The last 30 days
The last 30 days is the second of the four windows Microsoft lists for its usage reports. It is long enough to make a single unusual week less decisive, so use it for questions about the seller's regular routine rather than their latest week.
Microsoft's overview gives an example of what this kind of report can show: "For example, you can see who uses a service to the fullest extent and who barely uses it and might not need a Microsoft 365 license." ( Microsoft Learn: usage reports overview) That example is the reason a 30-day view can come up in a license conversation.
Be careful with that conclusion. A light user in one window may be a seller whose role does not need that service, a seller who is still learning it, or a seller whose main work sits in another tool. Each of these is a different conversation. Ask which one applies before you write anything about licenses.
Heavy use deserves the same care. A seller who relies on a service heavily may depend on it for work you have not discussed yet, and that reliance matters for their workload and for any changes you plan. Ask what the service does for them and what would happen if it were disrupted.
Think about the 30-day view as a rhythm check. If a supported breakdown shows changes within the month, does use stay steady or jump around? A steady pattern gives you something to discuss about routines. A jumpy pattern is a prompt to ask what drives the peaks and gaps, such as customer deadlines, quarter-end work, or a shared project that only runs for part of the month.
When you raise the 30-day view with the seller, bring any supported pattern alongside the total. Describe what you see in plain words, such as "your use of one tool is steady and another is light," only if the available detail supports that description. Hold any license decision until you have talked it through with the seller and checked the view again later.
The last 90 days
The last 90 days is the third of the four windows. Use it when you are asking whether activity has held up over several weeks rather than in a single stretch. It gives you more history than the 30-day view, but identifying a shift requires a supported breakdown.
For a new seller, a 90-day view may include the onboarding period as well as the first real work. Read onboarding weeks separately only if a supported weekly breakdown is available; otherwise use documented onboarding dates and observations as context. If the pattern changes once onboarding ends, that change is a question for the check-in. If the pattern stays the same, ask whether the early routine has held.
Compare the shape of the window with what the seller described during onboarding. Did they talk through which tools they would use, and in what order? Ask the seller whether the plan matches the work, using available usage totals only as context. Keep the conversation on the plan and on what got in the way, not on a score.
Be careful with a single total for the window. A total can hide a sharp change in the middle of the period, and that change can be the most useful thing to ask about. Look at individual weeks only if an available, supported breakdown allows it. A flat total can hide one busy stretch and one quiet one, and each has a different explanation.
Keep notes on the 90-day reading in a form you can compare later. When you pull the window again, you will want to see whether the pattern you noted has moved. A short table with the window, the pull date, and two or three observations is enough for that comparison.
Finally, ask the seller what they would have done differently in the first weeks. Their answer may point to a training need or a missing contact, which is more useful than any single figure in the report.
The last 180 days
The last 180 days is the longest of the four windows that Microsoft says its usage reports are generally available for. ( Microsoft Learn: usage reports overview)
If the seller started fewer than 180 days ago, this window reaches back before their start date. Days before the seller joined should not count against them, so check the start date against the window before you read it as a history of their work. A long window with a short tenure can look like an empty first half, and that tells you about the dates, not about the person.
Use the 180-day view for context. Discuss busy seasons, quiet months, or a product launch using your customer calendar; identify related usage patterns only if a supported breakdown allows it. Ask the seller how those periods felt from their side. Their answer will tell you more than the pattern alone.
Do not use the 180-day view to rank the seller against colleagues. Usage can differ for many reasons, including the accounts a person inherits, the customers they were assigned, and the projects they joined partway through. A comparison with colleagues treats those differences as if they were effort, and that is a weak basis for a check-in.
Because this window overlaps the shorter ones, read it last and tie it back to what you found in the 7-day, 30-day, and 90-day views. If the long view agrees with the shorter ones, you have a steadier basis for the conversation. If it disagrees, the disagreement is the thing to explore with the seller.
Illustrative example: compare the periods
Suppose a seller has been in the role for 30 days. The 180-day window includes time before they joined, so note their start date before interpreting it. Read the 30-day view alongside their account of onboarding. If usage looks light, ask about access and training rather than treating the total as a performance score.
How to use the four windows in the check-in
Use the 7-day and 30-day windows for questions about recent work, and the 90-day and 180-day windows for questions about the seller's first months. That split keeps each question in the period it fits, and it stops a single week from carrying more weight than it can bear.
Before the meeting, write one question for each window. For example: What happened in the last week? What is the 30-day pattern for the tools the seller is expected to use? Does the 90-day pattern match the onboarding plan? What does the 180-day view show about the start date and the customer calendar? Writing the questions first keeps the meeting on the seller's work rather than on a chart.
Bring the timing and window notes you wrote down earlier. Ask the seller to walk you through their own account of each period, and let that account shape how you read the numbers. Usage data covers only the services it tracks, so the rest of the seller's work belongs in the conversation. That includes customer calls, planning, research, and anything done outside those tools.
Agree on what to check next and when. If a timing gap caused a question, schedule a second pull after the report has had time to fill in, and read it again with the seller. Write down the window, the date, and the answer. For the next conversation, use coaching follow-up tasks to organise the agreed actions.
Today, choose a report window, record its pull time, and write the question you want to discuss with the seller.
Related guides: New-seller onboarding time: track it with 3 milestone parts · Form I-9 timing: 3 checks for a new seller · Check the $680 poster penalty before a new seller starts.
Questions to avoid in the first check-in
Should I ask why usage is low?
No; avoid questions that treat one number as a verdict, such as "Why is your usage so low?" A question like that assumes the number is accurate, complete, and fully within the seller's control. A better version names the window and the period: "The last 7 days looks light. What was going on that week?"
Should I compare the seller with a colleague?
No; avoid questions that compare the seller with a colleague in the same report. A comparison makes the meeting about ranking, and it skips the more useful question of what the seller needs to do the job. If you want to know how a process works across the team, ask that question separately, and keep the seller's numbers out of it.
Should I ask the seller to predict usage?
No; avoid questions that ask the seller to predict a number. Asking "How many times will you use the tool next month?" invites a guess and a defensive answer. Ask about plans instead: which customers they expect to work with, which tools those customers use, and what they need from you to get started.