Microsoft 365 Usage Analytics - data are not showing in dashboard for 2026

[poulraevdal]

We have been using the Microsoft App "Microsoft 365 Usage Analytics" in Power BI and also in Power Bi online.
Everything is setup and data refresh is running but data is not shown for 2026. it worked perfectly in 2025 showing all the changes and data throughout the year. 

I can see in the tables that it is picking up 2026 data but the dashboard does not show the numbers, dates, employes etc.

i have reinstalled the app several times and reconnected the Oauth2.0 connection to get the data which runs succesful. 
But since the data is there it seems that something wrong with the dashboard or can someone guide me in showing 2026 data
Thanks in advance
Poul

[Tchuko]

Hello,

I deleted MailboxStorageUsed and TotalIssueWarningQuota(KB/MB/GB/TB) form the Data and changed the Date formula to Calendar = CALENDAR(DATE(2016,1,1), TODAY()) and the 2026 january info loaded except for on tile in the usage report.

Hope it helps.

[Ritaf1983]

Hi @poulraevdal 

Most likely this is not an OAuth / reinstall issue. If you can see 2026 rows in the tables but the visuals show blanks, the report is filtering them out via the date dimension or report-level filters.

Things to check (in order):

Date/Calendar table coverage: In Data/Model view, check the max date in the report’s Calendar/Date table. If it ends at 2025-12-31, all visuals using that Calendar will return blank for 2026. Extend the Calendar to include 2026 (or build it dynamically based on MAX(Fact[Date])), then ensure relationships still point to that Calendar.

Report/Page filters & slicers/bookmarks: Open the Filters pane and look for any Year=2025 / “previous year” / “last 12 months” filters at visual/page/report level. Also use “Reset to default” to clear bookmark-stuck slicers.

Relationships / data type: Ensure the fact date column is Date (not DateTime) and is correctly related to the Calendar date column. If the fact column is DateTime, create a Date-only column (or convert in Power Query) and relate that to the Calendar.

Quick test: Create a simple table visual using only the fact table fields (including the date) without any Calendar fields. If 2026 shows there but disappears as soon as you use Calendar fields, it confirms the Calendar/filter issue.

If after these checks the built-in Microsoft template report is hardcoded to 2025, the workaround is to create a new report from the same dataset (or edit the model) with a corrected Calendar

If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly

[poulraevdal]

Hi Rita
Thanks for replying.

I can confirm that it is nothing to do with OAuth and getting the data. I can see data from 2026.

The Calender table have a filter 

Calendar = CALENDAR(DATE(2016,1,1),DATE(2025,12,31)) which is causing the issue.

But if i change to 

Calendar = CALENDAR(DATE(2016,1,1),DATE(2026,12,31)) i get an error 

I suppose this is the problem but unable to correct it.

Regards

Poul

[v-hjannapu · Accepted solution]

Hi @poulraevdal  ,
Thank you for reaching out to the Microsoft Community Forum.

The Microsoft 365 Usage Analytics report you installed is a template app and its dataset model including the Calendar table is controlled by the app. When you try to change the Calendar definition inside the installed app report, Power BI attempts to recompute dependent calculated columns and internal template logic, which results in the validation error you are seeing. In short, the calendar expression itself is not wrong, the template model simply does not allow that modification safely.

Create your own customized version of the dataset/report instead of editing the installed app model. Download the Microsoft-provided Usage Analytics PBIX, open it in Power BI Desktop, change the calendar to a dynamic definition such as: Calendar = CALENDAR(DATE(2016,1,1), TODAY()).nPublish this as your own dataset and build reports on top of it. Once the model is under your control, the 2026 data will appear normally and will continue working automatically for future years.

Hope the above provided information help you resolve the issue, if you have any further concerns or queries, please feel free to reach out to us.

 Regards,
Community Support Team.

[v-hjannapu]

Hi @poulraevdal,
I hope the information provided above assists you in resolving the issue. If you have any additional questions or concerns, please do not hesitate to contact us. We are here to support you and will be happy to help with any further assistance you may need.

Regards,
Community Support Team.

[poulraevdal]

Hi @v-hjannapu 
There came an update for the template which now goes to 2035 - perfect.
Can i ask for another thing which is the Company data which is not shown - it seems that company data are not picked up from the https://reports.office.com/pbi/v1.0/(tenant-ID)

because the table are empty - i check in intune and company data field have data in the field called "Company name". Strange that the template don't know how to pick up data from the company field.

Looking forward to hear from you 
Regards
Poul

[Narah]

We're having the same issue with missing company field data. M365 has the company field populated - it can be seen in Entra. However the reporting endpoint shows the field as null for all users. We have a support ticket logged but it's progressing slowly - there certainly seems to be an issue with the company field at the data source. It did previously work.

[poulraevdal]

Perfect, let me know when you have en update. I think city have same issue.

the underlaying data do not have the data 

[Narah]

@poulraevdal the update isn't a good one. After over a month of back and forth with support they advised that as of March 2026 Company is no longer supported in the Microsoft 365 Usage Analytics. Despite the template app still containing Company as a major indicator within the usage.

As you and I both know Company stopped working in at least February and possibly before and this seems like a retrospective withdrawal because something has broken that they can't or won't fix.

They've added an announcement to this page Microsoft 365 usage analytics overview - Microsoft 365 admin | Microsoft Learn

However as of the date of this post the data model page Microsoft 365 Usage Analytics Data Model - Microsoft 365 admin | Microsoft Learn still shows Company.

The alternative I've been given is to use Graph API to retrieve this data which is interesting as it isn't directly supported in Power Query and given the scale of my data and the refresh interval it's likely to need additional licenses. I've a call with an engineer scheduled to discuss.

[Narah]

After a lot of pain our ticket is with the product group. I'd strongly recommend logging a ticket if you haven't already - and anyone else who is experiencing the same issue.

We don't use City in Entra so I can't confirm it has the same issue but I can see it shows Null rather than an empty string which is how our other blank entries show.

[v-hjannapu]

Hi @poulraevdal,

Good to know the calendar issue is fixed after the update.

Regarding the Company data  this template does not directly read data from Intune tables. It only uses the data that comes from the Microsoft 365 usage reporting service reports.office.com endpoint.

So even if you see Company name filled in Intune, that field will appear in the report only if it is part of the usage analytics dataset returned by the reporting API. If the Company table inside the app is empty, it means that field is not coming through the usage reports data model.

The template cannot automatically pick additional fields from Intune or other sources. It only shows what is available in the dataset behind the app.

You can quickly check this in Data view and confirm whether the Company column is actually populated in the usage tables. If it is blank there, then the report is just reflecting the source data.

Regards,
Community Support Team

[DanieleUgoCopp]

Hello,

I would start by checking the Date table in the dataset behind the Microsoft 365 Usage Analytics app and if it does not extend into 2026 the visuals will automatically exclude that year even though the raw tables contain the data.

If the calendar already includes 2026, I would then review report level, page level, and visual level filters, especially year slicers or relative date filters that may still be restricted to 2025, since those can silently block the new year.

Thank you
Best regards,
Daniele