Conditional Access Problems

How to Configure Azure MFA and Conditional Access for Lifecycle Services

Anum Mushtaq Oct 20, 2026 868 views

Question details

The user needs to configure Azure Multifactor Authentication (MFA) via Conditional Access for Lifecycle Services (LCS) and resolve an issue where the Submit Incident page appears blank.

How to Configure Azure MFA and Conditional Access for Lifecycle Services

Product: Azure Active Directory / Lifecycle Services
Device & OS: not provided
Scenario: Enforcing multifactor authentication for Lifecycle Services when the application is not directly selectable in the Conditional Access app list.
Observed behavior: Lifecycle Services (LCS) does not appear as a selectable cloud app in Conditional Access policies, and users attempting to submit incidents may encounter a blank page due to authentication, caching, or permission conflicts.

Before you start

Ensure you have Azure Active Directory administrator privileges and verify that the affected user has the appropriate Lifecycle Services (LCS) role and customer-project permissions assigned.

Solution 1Recommended

Enforce MFA using an 'All Cloud Apps' Conditional Access Policy

Since LCS is not explicitly listed in the Conditional Access app selection, use a broad policy targeting all cloud applications to enforce multifactor authentication.

Microsoft Lifecycle Services (LCS) may appear under Enterprise Applications but frequently lacks a direct entry in the Conditional Access application selection list. To ensure LCS sign-ins are protected, you must deploy a policy that covers all cloud applications.

Access Azure Active Directory

Log in to the Azure Portal as a Global Administrator or Conditional Access Administrator and navigate to Azure Active Directory > Security > Conditional Access.

Configure App Targeting

Create a new policy or edit your existing general MFA policy. Under 'Cloud apps or actions', select 'Include' and choose 'All cloud apps' rather than searching for LCS specifically.

Set Access Controls

Under 'Access controls', select 'Grant access' and check the 'Require multifactor authentication' box. Save and enable the policy.

Enforce MFA using an 'All Cloud Apps' Conditional Access Policy

Avoid Permanent Exclusions: Do not exclude affected users from the general MFA policy to bypass LCS login issues. This removes their security protection and should only be used momentarily as a diagnostic test.

Solution 2

Resolve the Blank Submit Incident Page in LCS

Fix blank page rendering issues in LCS by clearing cached credentials and validating user authorization.

Free Microsoft Office alternative

Streamline Your Workflow with WPS Office

While you manage complex Azure infrastructure and Conditional Access policies, simplify your daily documentation with WPS Office. It provides a highly compatible, fast, and free alternative to Microsoft Office for all your Word, Excel, and PowerPoint needs.

1. Download the Installer: Visit the official WPS Office website and download the free installation package for your operating system.
2. Install WPS Office: Run the downloaded installer and follow the quick on-screen instructions to set up the suite on your computer.
3. Open Your Documents: Launch WPS Office and open your existing Microsoft Office formats (.docx, .xlsx, .pptx) directly with full formatting preserved.

Free and lightweight office suite with a minimal system footprintSeamless format compatibility with Microsoft Word, Excel, and PowerPoint filesFamiliar, tabbed user interface requiring zero learning curve for Office usersBuilt-in PDF editing, conversion, and cloud collaboration tools

microsoft office alternative - wps office

Frequently Asked Questions

Why is Lifecycle Services missing from the Conditional Access app list?

Microsoft does not expose all backend services, including Lifecycle Services (LCS), as individual selectable apps in Conditional Access. To enforce MFA on these services, you must apply a policy targeting 'All cloud apps'.

Can I exclude a user from MFA to fix LCS access problems?

While excluding a user from the MFA policy might temporarily bypass a login loop or blank page, it is highly discouraged. Doing so removes essential account protection and should only be used briefly as a diagnostic step to confirm if MFA is the root cause.

What causes the Submit Incident page in LCS to load as a blank screen?

A blank Submit Incident page typically results from conflicting cached browser credentials, insufficient LCS project permissions, missing user roles, or temporary Microsoft service outages. Testing in an Incognito/InPrivate window helps isolate caching issues.

Microsoft Office Security Issues