> 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/analyzer/deprecation-radar.md).

# Deprecation Radar

## What it does

Every few months Microsoft retires something with a hard date, and every tenant has to find out which of its own objects break. The Deprecation Radar shows you which groups and assignment filters in your tenant use something Microsoft is about to stop supporting, by when, and which policies, apps and Conditional Access policies depend on them.

Today it checks two things:

* **Dynamic groups that use the memberOf operator.** Microsoft Entra stops updating these groups after 3 November 2026. They stay in their last known state, so the people in them can keep, or miss, access that policies, apps and Conditional Access policies give to the group.
* **Assignment filters that still use the osVersion property.** Microsoft deprecated this property in favour of operatingSystemVersion. Existing filters keep working for now, and Microsoft has not published a removal date.

Seeing the findings is free. The radar reads your tenant each time and stores nothing.

## How to use it

1. Open the **Tenant Overview** page. After the overview has finished collecting, a **Deprecated** card shows the first findings and how many are due within 30 days.
2. Select **View all**, or go to **Settings Library, Settings Catalog, Tenant Impact** and open the **Objects and devices** tab.
3. Select a finding to see its consumers: the policies, apps and Conditional Access policies that target the group or use the filter.
4. Use **Read Microsoft's information** on a finding to open Microsoft's page about the retirement in a new tab.
5. Use **Export** to download a CSV with one row for each finding and consumer.
6. After you create or change a group, select **Refresh from Microsoft Graph**. Your groups are cached for up to an hour, so a change can take that long to show without a refresh.

You also see the radar where you work with assignments. On the assignments overview, the group, filter and app assignment pages:

* A banner above the table says how many of the listed groups are affected and when they stop being supported.
* Under each affected group in the Target column, a warning shows the date and a link to the details and to Microsoft's information.

## What you will see

* **Findings.** One card for each group or filter, with the deadline and the number of days left. A filter without a published date shows "No date published".
* **Consumers.** For each consumer you see its name, its type (policy, app or Conditional Access), whether the group is assigned, excluded or included, and whether the consumer targets the group directly or through a parent group that contains it.
* **Groups nobody uses.** They are still listed, with no consumers, so you can clean them up.
* **Warnings.** If something could not be read, a yellow note says what is missing. For example, when consent for reading Conditional Access policies has not been given, Conditional Access policies are not listed as consumers, but everything else is.

## Requirements

* An active Intune Assistant customer. No extra module is needed.
* Permission to read your groups, device configuration and apps, as for the other assignment pages. Listing Conditional Access policies as consumers needs consent for reading Conditional Access policies. Without it, the rest of the radar still works.
* Managed service providers see the findings of the tenant they have selected, not their own.

## Common questions

**Why is my new group not in the list?** The list of groups is cached for up to an hour. Select **Refresh from Microsoft Graph** on the Objects and devices tab.

**Does a group that only mentions the word memberOf in a value show up?** No. Only rules that use the operator are flagged. A rule such as a department equal to the word memberOf is not.

**Why does a policy show "Via" another group?** The policy is assigned to a parent group that contains the affected group, so it still reaches the people in the affected group.

**Can it fix the groups for me?** Not yet. Keeping the findings over time, alerts and a bulk fix are planned as separate, licensed additions.

**What should I do with an affected group?** Microsoft's guidance is to replace the memberOf operator with supported rule operators, or to convert the group to assigned membership, and then check the membership.
