📋 Microsoft Entra Documentation Changes

 

---

 

## March 2025

 

### Microsoft Entra Permissions Management end of sale and retirement

 

---

 

> Branding themes for applications are currently in PREVIEW.

> This information relates to a prerelease product that may be substantially modified before it's released. Microsoft makes no warranties, expressed or implied, with respect to the information provided here.

 

 

This article describes how you can create multiple branding themes for different applications in your tenant.

 

 

Branding themes build on neutral branding and default branding.

 

 

Here are some important things to know about how branding themes work.

 

:::image type="content" source="./media/how-to-customize-branding-themes-apps/languages-tab.png" alt-text="Screenshot of the Languages tab to add a language." lightbox="./media/how-to-customize-branding-themes-apps/languages-tab.png":::

 

## Related content

---

description: This article discusses how to use Custom Attribute Triggers as an attribute change trigger within a workflow in Lifecycle Workflows.

author: owinfreyATL

ms.author: owinfrey

 

 

 

 

Lifecycle Workflows allows you to trigger workflows to run automatically for users that meet the execution conditions of the workflow. There are many default attributes that you can use to trigger workflows, but sometimes you might require triggering a workflow based on a specific attribute not offered by default. Using custom attribute triggers, you can trigger a workflow to run for users based on when they move within your organization based on:

 

- [Custom security attributes (CSA)](manage-workflow-custom-security-attribute.md)

 

## Prerequisites

 

[!INCLUDE [Microsoft Entra ID Governance license](../includes/entra-entra-governance-license.md)]

 

To identify Intune device compliance and app protection policies, the agent must be running as a Global Administrator or Conditional Access Administrator AND Global Reader. Conditional Access Administrator isn't sufficient on its own for the agent to produce Intune suggestions.

 

## Remove agent

 

If you no longer wish to use the Conditional Access optimization agent, select **Remove agent** from the top of the agent window. The existing data (agent activity, suggestions, and metrics) is removed but any policies created or updated based on the agent suggestions remain intact. Previously applied suggestions remain unchanged so you can continue to use the policies created or modified by the agent.

ms.service: entra-id

ms.subservice: app-provisioning

ms.topic: how-to

ms.author: jfields

ms.reviewer: chmutali

ai-usage: ai-assisted

 

## Job configuration

 

> [!IMPORTANT]

> Test the configuration changes described in this document in your test environment, before enabling the configuration in your production setup.

 

1. Open your Workday-to-AD/Microsoft Entra ID provisioning job.

 

ms.service: entra-id

ms.subservice: authentication

ms.topic: article

 

 

ms.author: justinha

|Workday Writeback | ✅ |

|SuccessFactors to Microsoft Entra user provisioning | ✅ |

|SuccessFactors to Writeback | ✅ |

|Provisioning agent configuration and registration with Gov cloud tenant| Works with special undocumented command-line invocation:<br> `AADConnectProvisioningAgent.Installer.exe ENVIRONMENTNAME=AzureUSGovernment` |

 

## Other Microsoft Entra products

[!INCLUDE [21796](../includes/secure-recommendations/21796.md)]

 

### Temporary access pass is enabled

 

### Restrict Temporary Access Pass to Single Use

[!INCLUDE [21846](../includes/secure-recommendations/21846.md)]

[!INCLUDE [21844](../includes/secure-recommendations/21844.md)]

 

### Enable Microsoft Entra ID security defaults

author: kenwith

manager: dougeby

ms.topic: overview

ms.service: global-secure-access

ms.reviewer: abhijeetsinha

ai-usage: ai-assisted

| Partner | Partner documentation | Description |

|----------------|-----------------------|----------------|

| Arista Networks | [Arista deployment guide](https://www.arista.com/assets/data/pdf/microsoft-entra-internet-access-with-arista-cv-pathfinder.pdf) | Arista Networks integrates Microsoft Entra Internet Access with Arista CloudVision Pathfinder to deliver secure internet access to Arista Data Center, Campus, Branch, and remote locations. Arista WAN Routing Systems intelligently routes traffic to Microsoft's SASE platform for inspection, ensuring secure internet and SaaS access. |

| Check Point | [Check Point configuration guide](https://support.checkpoint.com/results/sk/sk182799) | Check Point's Quantum SD-WAN solution brings advanced security to WAN connectivity, seamlessly integrating with Microsoft's SASE platform to optimize and secure Microsoft 365 and internet traffic for customers across distributed locations. This solution combines threat prevention, intelligent traffic management, and streamlined workflows, reducing complexity and strengthening security posture across both network and cloud environments. |

| Cisco Catalyst | [Cisco Catalyst user guide](https://www.cisco.com/c/en/us/solutions/collateral/enterprise-networks/sd-wan/catalyst-sd-wan-ms-sse-int-ug.html) | The Cisco Catalyst SD-WAN integrations with Microsoft's SASE platform use simplified network deployment and advanced threat protection capabilities to deliver comprehensive security for internet-bound traffic originating from branch offices. All internet traffic is routed to Microsoft's SASE platform for inspection, safeguarding users, devices, and data from evolving threats while securing public internet and SaaS access. |

| Cisco Meraki | [Meraki configuration guide](https://documentation.meraki.com/MX/Security_Service_Edge_Integrations/Meraki_Secure_SD-WAN_Microsoft_SSE_Configuration_Guide) |The Cisco Meraki SD-WAN integrations with Microsoft's SASE platform use simplified network deployment and advanced threat protection capabilities to deliver comprehensive security for internet-bound traffic originating from branch offices. All internet traffic is routed to Microsoft's SASE platform for inspection, safeguarding users, devices, and data from evolving threats while securing public internet and SaaS access. |

---

 

 

 

Workflows by default, unless specified during creation, are managed by users with either the Lifecycle Workflows, or Global, administrator roles. As workflows grow and change to meet the needs of members of your organization, so does the need to limit who can manage them. With delegated workflow management, you can scope management of workflows using [Administrative Units](../identity/role-based-access-control/administrative-units.md). When scoped, specific admins are only granted access to manage specific workflows. Scoping allows for greater security within your environment by following Microsoft's least privileged access guidelines by only giving access to specifically what's needed.

 

 

7. Update the desired properties.

> [!NOTE]

 

8. Select **save**.