New policy

This page describes the policy creation experience in EasyLife 365 Identity, focusing on how to configure policy rules using the admin portal.

Create a new policy

To create a new policy:

1. Navigate to Policies in the admin portal.
2. Select Create new.
3. Choose the policy type:
   • App Registration Policy
   • Enterprise Application Policy

After selecting a type, the Create policy page opens.

Create policy layout

The policy editor is divided into two main areas:

• Left navigation panel: used to move between configuration sections
• Main content area: used to configure the selected section

A warning indicator appears next to sections that are incomplete or invalid.

Configuration sections

1. General

The General section captures basic policy metadata.

Field	Description	Required
Title	The display name of the policy. Shown in the policy list and used when assigning policies.	Yes
Description	A brief explanation of the policy's purpose.	No
Status	Whether the policy is Active or Inactive. Only active policies are enforced.	Yes

2. Rules

The Rules section defines the compliance criteria that applications must satisfy.

Administrators can configure one or more of the following rules:

Minimum application owner

Requires an application to have at least X application owners sourced from Microsoft Entra ID.

• Configuration: Specify the minimum number of required owners (default: 1)
• Purpose: Ensures that full administrative responsibility is never concentrated in a single account or missing entirely

Minimum technical owner

Requires an application to have at least X technical owners assigned in EasyLife 365 Identity.

• Configuration: Specify the minimum number of required technical owners
• Purpose: Provides delegated operational coverage without granting full Entra ID ownership

Minimum business owner

Requires an application to have at least X business owners assigned in EasyLife 365 Identity.

• Configuration: Specify the minimum number of required business owners
• Purpose: Establishes non-technical accountability and ensures every application has a clear business sponsor

Activity rule (Enterprise Applications only) Professional

Requires an enterprise application to have been signed in to within the last X days.

• Configuration: Specify the maximum number of days since last sign-in
• Purpose: Helps identify unused or obsolete integrations
• Availability: Enterprise Application policies only
• Plan: Professional plan required

info

An application is considered compliant only if it satisfies all rules defined in the policy.

3. Notifications

The Notifications section controls how owners are alerted about non-compliant applications.

Field	Description
Number of notifications	How many notifications to send before triggering escalation actions.
Days between notifications	The interval (in days) between successive notifications.

4. Escalation

The Escalation section defines what happens when an application remains non-compliant after all notifications have been sent.

Administrators can configure one or more escalation actions:

Email escalation

Send an email to a specified address when escalation is triggered.

Field	Description
Recipient email	The email address to notify.
Subject	The email subject line.
Body	The email message content. Supports placeholders for application details.

Webhook escalation

Send an HTTP POST request to an external system when escalation is triggered.

Field	Description
Webhook URL	The endpoint to call.
Headers	Optional HTTP headers (e.g., for authentication).
Body	The JSON payload. Supports placeholders for application details.

Saving the policy

After configuring all sections:

1. Review the policy configuration for completeness.
2. Click Save to create the policy.
3. If any required fields are missing, the system will highlight them with a warning indicator.

Once saved, the policy will appear in the policies list and can be assigned to applications.

Setting a default policy

To set a policy as the default:

1. Navigate to the policy list.
2. Click the three-dot menu on the desired policy.
3. Select Set as default.

The default policy will be automatically applied to all applications without an explicitly assigned policy.