> For the complete documentation index, see [llms.txt](https://docs.intuneassistant.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intuneassistant.cloud/intune-assistant/tenant-overview.md). # Tenant Overview ## What Is This Page? The **Tenant Overview** page is the starting point of Intune Assistant. As soon as you sign in, Intune Assistant starts loading every configuration in your Intune tenant in the background — Settings Catalog policies, device configuration profiles, administrative templates, compliance policies, app protection and app configuration policies, scripts and remediations, Windows update profiles, enrollment configurations, Autopilot profiles, disk encryption policies, iOS app provisioning profiles and applications. While that happens, a small status window in the bottom-right corner shows each resource type being fetched, ticking them off one by one. When it is done, the overview page shows totals, how much of it is assigned, a breakdown per resource type and per platform, and a searchable inventory of everything that was found. The result is kept for **30 minutes**, so navigating around the app or reloading the page inside that window is instant — nothing is fetched again until you press **Refresh data** or the data goes stale. The **Configuration Assignments (all)** page uses the same data, so it opens already filled in, the **Backup** page uses it to know what exists before it starts exporting, and the **Search tenant** box in the sidebar (or **Ctrl+K** / **⌘K** anywhere) searches all of it without waiting. *** ## Why Would You Use This? * You want a single, instant answer to "what is in this tenant?" without opening every Intune blade * You want to spot configuration types that exist but are not assigned to anything * You are handing over or reviewing a tenant and need a quick shape of it: how many policies, of which types, for which platforms * You want to search across every configuration type at once by name, description, platform or type *** ## How to Load the Data {% stepper %} {% step %} ### Sign in Loading starts automatically the first time you sign in, and again whenever the data is older than 30 minutes. You do not have to open the overview page for this to happen. {% endstep %} {% step %} ### Watch the status window A panel appears in the bottom-right corner listing every resource type. A spinner means it is still loading, a green check means it is done (with the number of items found), and a red cross means that type could not be loaded. The panel folds itself away a few seconds after a clean run; if something failed it stays open so you can see what. {% endstep %} {% step %} ### Open **Intune Assistant → Tenant Overview** Everything that has already arrived is shown immediately, and the page fills in as the remaining types finish. {% endstep %} {% endstepper %} *** ## What You'll See * **Data collected … ago** in the top-right corner, with a **Refresh recommended** hint once the data is older than 30 minutes, and a **Refresh data** button to fetch everything again. * **Reset cache** next to it throws away everything collected for this tenant, in memory and on disk (including any backup content kept ready for the Backup page), and collects it again from scratch. Use it when you want to be certain nothing old is left over; **Refresh data** keeps the previous data visible until the new collection completes. * **Total configurations**, **Assigned** (with the number that is not assigned and the number of built-in tenant defaults), **Configuration types** and **Data loaded** cards. * **Changes since last collection** — what differs from the previous time this tenant was collected: configurations that were created, deleted, renamed or modified, and assignments that were added or removed. See [What changed](#what-changed-since-last-time) below. * **Resource types** — one bar per type showing how many items were found and how many of those are assigned. * **By platform** — a donut of where your configurations apply (Windows, iOS, macOS, Android, …). * **All configurations** — every item grouped by type. Expand a type to see each item's name, platform, sub-type, assignment state, last-modified date and how many settings or assignments it has. Use the search box to filter across every type at once; sections that contain a match open automatically. ### Item details Click any configuration name in the **All configurations** list to open its details on the right: * **Assignments** - every target with the group name, include or exclude, the filter applied (with its name) and any warning such as a deleted group. Click a group to open its details; **Open in Configuration Assignments** jumps to the assignments page filtered to this item. * **Configuration** - the item's settings as Intune stores them, shown as readable properties (nested settings fold open) or as raw JSON, with a copy button. For an Autopilot profile, for example, that is the device name template, language, out-of-box experience and enrollment status page settings and the hardware-hash setting; for a compliance policy the rules; for a script its schedule and run context. The configuration is fetched from Intune the first time you open an item and reused afterwards; when the Backup page's **Keep backup content ready** switch is on, it is already there. The small text next to the heading says where it came from, and the refresh icon fetches it again. Resource kinds without a configuration payload (connectors, roles, categories) show the assignments part only. ### Assignment states * **Assigned** — at least one assignment an administrator created. * **Not assigned** — the configuration exists but applies to nobody. * **Tenant default** — Intune's built-in "All users and all devices" enrollment defaults. They apply everywhere but nobody assigned them and they cannot be removed, so they are not counted as assigned. * **Not configured** — assigned but switched off (for example a Windows Hello for Business enrollment configuration set to *Not configured*), so it has no effect. ### What changed since last time Change history is part of the **Configuration Management** module. Without it, the overview page shows a small locked card in its place and the history page is unavailable; Intune Assistant does not store anything about your tenant for this: the history starts the day the module is activated. Every time the overview is collected, Intune Assistant compares it with the previous collection of the same tenant and keeps the differences. The **Changes since last collection** card on the overview page shows them for the latest collection, with a coloured badge per kind: | Badge | Meaning | | ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | | **Created** | A configuration exists now that did not exist in the previous collection | | **Deleted** | A configuration from the previous collection is gone | | **Renamed** | Same configuration, new name (the old name is shown) | | **Modified** | Same name, but Intune reports it was changed since the previous collection, or its scope tags changed (the added and removed tags are listed) | | **Assignment added** | The configuration now targets a group, all users or all devices it did not target before (or now excludes one) | | **Assignment removed** | A target it had before is gone | Assignment changes name the group and filter involved. Click a configuration name to find it in the overview, or a group target to open the group's details. The status window in the bottom-right corner also shows the number of changes when a collection finishes. **View history** (also under **Tenant Overview → Change history** in the sidebar) opens the investigation page: a timeline of every change of the last 24 hours, 7, 30 or 90 days on the left, grouped per collection, and the details of the selected change on the right. History is kept for 90 days. For every change Intune Assistant looks up the matching entry in the **Intune audit log** and shows: * **Who and when** - the user (or the application) that made the change and the exact time Intune recorded it, next to the time Intune Assistant detected it. The timeline shows the user next to each change, and **Everyone** at the top filters the log to one person. * **What changed** - the properties Intune reported as changed, with their value before and after. For assignment changes the target group and filter are named; for renames the old and new name. * **Audit record** - the audit event id (linked to the Audit Events page), the correlation id and the resource id, for when you need to follow up in Microsoft's own tooling. Intune publishes audit events with a delay of a few minutes, so a change detected right after it was made can show "No Intune audit event was found yet". Press **Check audit log** on that change to look again. A change without a matching event still shows everything Intune Assistant knows from the comparison itself. One limit to know: for each collection Intune Assistant reads at most the **5,000 newest audit events** between the two collections. That is far more than a normal 30-minute window holds, but a tenant that was not collected for days can exceed it. A change that could not be matched for that reason says so explicitly ("more than 5,000 audit events…") and offers a link to the **Audit Events** page, where you can search the resource id shown on the change yourself. Two things to know: * Changes are detected **when the overview is collected**, not the moment they happen in Intune. If nobody collects the tenant for a day, everything that happened in that day shows up in one batch at the next collection. Press **Refresh data** after making changes to see them right away. * The very first collection of a tenant is the baseline; it has nothing to compare against, so the card says so and the differences start with the second collection. * If a whole resource type came back empty while the previous collection had several items - typically a call to Microsoft Graph that was throttled or failed - that type is **not compared** and the card says so under "Not compared this time". You will not see a wave of "deleted" entries followed by "created" ones at the next collection. ### Searching from anywhere Press **Ctrl+K** (Windows) or **⌘K** (Mac) on any page, or click **Search tenant…** at the top of the sidebar. Type part of a policy, profile, app, or group name. Results are split into **Configurations** and **Assignments**; picking one opens the page that owns it with the search already filled in. The search runs on the collected data, so it is instant and works offline from Intune until you refresh. *** ## Requirements * An active Intune Assistant customer account on the **beta channel** — the tenant overview, the global search and change history are being rolled out to beta customers first. Other customers do not see the Tenant Overview entry; the assignment pages keep working for them the way they did before. * The **Configuration Management** module for [change history](#what-changed-since-last-time). * The same Microsoft Graph read permissions the assignment pages use. If a permission is missing, the consent banner tells you which one; grant it and press **Refresh data**. *** ## Common Questions **Does the overview show live data?** It shows what was collected at the time shown in the top-right corner. Press **Refresh data** to fetch the latest state; the 30-minute window exists to keep the rest of the app fast, not because the data cannot be refreshed sooner. **One resource type shows a red cross — is the rest of the data still correct?** Yes. Each type is loaded independently. The types that loaded are complete; the failed one is simply missing and listed in the amber notice on the overview page. Press **Refresh data** to try again. **Is the cached data shared with colleagues?** The copy in your browser is yours alone, per signed-in account and per tenant, and is cleared when you sign out. With the **Configuration Management** module, Intune Assistant also keeps one shared copy per tenant on the server for 30 minutes, so when a colleague has just collected the same tenant you get that copy instantly instead of collecting again; the collected-at time then shows "(shared tenant snapshot)". That shared copy holds the same information the overview shows - names, types, platforms, dates and assignment targets - never policy settings. Without the module nothing is stored on the server: the overview is collected live, and the result is only held in the server's memory for a few minutes so that your colleagues' pages do not collect it again straight away. **Refresh data** always collects anew. **Can I start from a blank screen, for a demo or a screenshot?** Open `/overview?demo=1`. That clears everything collected for the tenant (including backup content), switches **Collect automatically at sign-in** off, and shows a **Start collecting** button so you decide when the stream begins. Switch auto-collect back on afterwards using the toggle on that same screen; the setting is remembered per browser. **A change shows as "Modified" but I only changed a setting - can I see which one?** Not here. The overview holds names, types, dates and assignments, not settings, so it knows *that* Intune reported a change, not what the change was. Use a **Monitor** on the policy for setting-level drift, or compare the policy's backup with the current state. **A resource type failed to load - will its items show as deleted?** No. A type that failed in either of the two collections being compared is left out of the comparison entirely, so a temporary Graph error never produces a wave of false "deleted" and "created" entries. **I switched tenants and the overview reloaded — why?** The overview belongs to one tenant. Switching tenants restores that tenant's own cached overview if it is less than 30 minutes old, otherwise it loads it fresh.