> 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/conditional-access/bulk-edit-ca-policies.md).

# Bulk Rename Conditional Access Policies

When your Conditional Access policies accumulate names that no longer match your standards — after a baseline update, a tenant migration, or simply over time — renaming them one by one is slow. Bulk Rename lets you apply naming changes across many policies at once, with a preview before anything is saved.

## What you can do

* **Add a prefix** — e.g. turn `MFA - All users` into `LEGACY - MFA - All users`
* **Add a suffix** — e.g. turn `MFA - All users` into `MFA - All users - v1`
* **Replace text** — e.g. change `DEV` to `PROD` across all selected policies

## How to use it

1. Go to **Conditional Access** and load your policies.
2. Select the checkboxes next to the policies you want to rename.
3. Click **Bulk Edit** in the selection toolbar that appears.
4. Choose your rename operation: **Add prefix**, **Add suffix**, or **Replace text**, then fill in the value.
5. Click **Preview Changes** to see exactly what will change before anything is saved.
6. Review the preview table — each row shows the current name and the proposed new name.
7. If everything looks right, click **Apply** to execute the changes.
8. After the changes are applied, you are automatically returned to the policy list after a few seconds.

## What you will see in the preview

The preview shows a table with one row per selected policy:

| Current name          | New name                       | Status   |
| --------------------- | ------------------------------ | -------- |
| `MFA - All users`     | `LEGACY - MFA - All users`     | Ready    |
| `Block - Legacy auth` | `LEGACY - Block - Legacy auth` | Conflict |

Rows marked as a conflict will be skipped during execution — the rest will proceed. A final result table is shown after applying.

## Requirements

* Available to all non-free customers (Standard with paid modules, Enterprise, MVP, NFR, MSP).
* MSP admins can run bulk renames on their managed customer tenants by selecting the correct tenant from the tenant switcher.
* You need the **Policy.ReadWrite.ConditionalAccess** Graph permission to rename policies. If IntuneAssistant has not been consented for this scope yet, you will be prompted to consent first.

## Safety rules

* You can only add a prefix, add a suffix, or replace specific text — you cannot overwrite the entire name to a fixed value.
* If the proposed new name already exists in the tenant, that policy is automatically skipped.
* All changes are recorded in the **Audit Log** so you can always see what was changed, when, and by whom.

## Tips

* Use **Replace** to fix a typo or update a version number across all matching policies at once.
* Run a preview first on a small selection to verify your pattern before applying to all matching policies.
* If you need to undo a rename, run Bulk Edit again with the reverse operation.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.intuneassistant.cloud/intune-assistant/conditional-access/bulk-edit-ca-policies.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.