Compliancemanzill.com
CIS Microsoft Azure Foundations Benchmark v1.4.0

CIS Microsoft Azure Foundations Benchmark v1.4.0/AppService/105 of 115

9.1Ensure App Service Authentication is set up for apps in Azure App Service

Control family: AppService

Control description

Azure App Service Authentication is a feature that can prevent anonymous HTTP requests from reaching the API app, or authenticate those that have tokens before they reach the API app. If an anonymous request is received from a browser, App Service will redirect to a logon page. To handle the logon process, a choice from a set of identity providers can be made, or a custom authentication mechanism can be implemented.

How to implement

ResponsibilityCustomerYou configure and operate this in your own cloud accounts.

App Service authentication signs users in before a request reaches the app, so anonymous requests never get through. It doesn't replace the app's own authorization, but it stops whole classes of attacks on unprotected endpoints.

Before you start

The same on every cloud, before the steps in the tabs.

  • Record in the App Service standard which apps require sign-in through App Service authentication, and which identity provider they use, so every new app and deployment slot starts with it.
  • Record any app that must stay anonymous, with its approver.

Evidence

  • The App Service configuration standard

On Azure the tasks add an identity provider and require sign-in in each app's Authentication settings, then keep it checked with the CIS standard.

Task 1Require sign-in with Microsoft Entra ID

  1. Sign in to the Azure portal at portal.azure.com and open App Services, then the app.
  2. Select Settings > Authentication, then Add identity provider.
  3. Choose Microsoft and create a new app registration (or pick an existing one).
  4. Under Action to take when request is not authenticated, choose to require sign-in: HTTP 302 Found redirect for websites or HTTP 401 Unauthorized for APIs.
  5. Select Add.
  6. Check it: opening the app in a private browser window sends you to the sign-in page.

Task 2Keep it checked with the CIS v1.4.0 standard in Defender for Cloud

  1. Open Microsoft Defender for Cloud > Regulatory compliance and select Manage compliance policies.
  2. Select the subscription, select Security policies, find CIS Microsoft Azure Foundations Benchmark v1.4.0 and toggle its status to On (once per subscription).
  3. Back on Regulatory compliance, open the CIS Microsoft Azure Foundations Benchmark v1.4.0 standard and expand recommendation 9.1.
  4. Open the assessment for App Service apps should have authentication enabled and Function apps should have authentication enabled and fix the resources it lists as non-compliant.
  5. Check it: every resource under recommendation 9.1 shows as passing after the next evaluation.

Evidence

  • The Authentication settings of each app, with a provider and sign-in required
  • The CIS v1.4.0 standard, with recommendation 9.1 passing

Console steps as of 5 November 2026. Not every step has been confirmed in a live console yet, and menus and labels can move between releases, so look for the nearest match if one has changed.