Service Name Mismatches

[timothymeyers]

The Service Names in the tables on this page do not always match up with the Service Level hierarchy of names that is reported in the Azure Health Report, nor with the simplified Service Level Hierarchy used on the Products By Region page.

Some examples:

• Azure App Service is a sophisticated capability with lots of various SKUs and configurations down to SL5. This page doesn't even name it with its proper name, simply calling out a single row for Web Apps (App Service). Are we to assume all App Services, inclusive of all plans and App Service Environments, and across Linux and Windows, are authorized? What about App Service - Static Web Apps?
• Azure Communication Services is not represented at all.
• Functions is only listed as a single row; should we assume all Function SKUs at SL4 are authorized (e.g. Linux v. Windows, Standard v. Premium)?
• Logic Apps is only listed as a single row; should we assume both the Standard and Consumption plans are authorized? What about Logic Apps Integration Accounts?

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 4e27d0b1-56f9-2eb7-8fee-0c47cfbafeac
• Version Independent ID: 12556227-6adc-52c1-ac60-f341ae247e51
• Content: Azure and other Microsoft cloud services compliance scope - Azure Government
• Content Source: articles/azure-government/compliance/azure-services-in-fedramp-auditscope.md
• Service: azure-government
• GitHub Login: @stevevi
• Microsoft Alias: stevevi

[YashikaTyagii]

@timothymeyers Thanks for your feedback! We will investigate and update as appropriate.

[stevevi]

Resolved offline with assistance from @Jain-Garima.

[stevevi]

please-close