Update b2c-or-tenant-premium-license-sign-in-activities.md

Edit review per CI 5503

Author: przlplx

support/entra/entra-id/users-groups-entra-apis/b2c-or-tenant-premium-license-sign-in-activities.md

@@ -1,19 +1,19 @@
 ---
-title: Tenant doesn't have premium license when querying user sign-in activities using Microsoft Graph
-description: Provides solutions to the "either tenant is B2C or tenant doesn't have premium license" error when you query user sign-in activities using Microsoft Graph
+title: Tenant doesn't have premium license When You Query User Sign-in Activities By Using Microsoft Graph
+description: Provides solutions to the "either tenant is B2C or tenant doesn't have premium license" error when you query user sign-in activities by using Microsoft Graph
 ms.date: 04/25/2025
 ms.service: entra-id
 ms.author: bachoang
 ms.custom: sap:Getting access denied errors (Authorization)
 ---
 
-# Neither tenant is B2C or tenant doesn't have premium license when querying sign-in activities
+# "Neither tenant is B2C or tenant doesn't have premium license" error when you query sign-in activities
 
-This article describes the error that occurs when you make Microsoft Graph API calls related to user sign-in activities or user registration details.
+This article discusses the error that occurs when you make Microsoft Graph API calls that are related to user sign-in activities or user registration details.
 
 ## Symptoms
 
-When you run one of the following Microsoft Graph API calls, you might see this error:
+You run one of the following Microsoft Graph API calls:
 
 ```http
 GET https://graph.microsoft.com/v1.0/auditLogs/signIns
@@ -23,7 +23,7 @@ GET https://graph.microsoft.com/v1.0/users?$select=displayName,userPrincipalName
 GET https://graph.microsoft.com/v1.0/reports/UserRegistrationDetails
 ```
 
-Example response
+After you run the call, your receive an error response that resembles the following text:
 
 ```output
 'error': {
@@ -36,18 +36,19 @@ Example response
     }
 }
 ```
+
 ## Solution
 
 ### Scenario 1: Query user sign-in activities
 
-1. Make sure the target tenant has an Entra ID Premium P1 or P2 license. In the Azure portal, go to **Microsoft Entra ID**, select Overview, and then check the **License**.  For more information, see [Sign up for Microsoft Entra ID P1 or P2 editions](/entra/fundamentals/get-started-premium).
-1. Verify that the Microsoft Graph Access Token has been granted the `AuditLog.Read.All` and `Directory.Read.All` permissions.
+1. Make sure that the target tenant has an Entra ID Premium P1 or P2 license. In the Azure portal, go to **Microsoft Entra ID**, select **Overview**, and then check the **License** value.  For more information, see [Sign up for Microsoft Entra ID P1 or P2 editions](/entra/fundamentals/get-started-premium).
+1. Verify that the Microsoft Graph Access Token was granted the `AuditLog.Read.All` and `Directory.Read.All` permissions.
 
 ### Scenario 2: Query credential user registration details
 
-1. Make sure the target tenant has an Entra ID Premium P1 or P2 license.
-1. Verify that the Microsoft Graph Access Token has been granted the `Reports.Read.All` permission.
-1. The authenticating user or the service principle of the application must be in one of these Administrative roles:
+1. Make sure that the target tenant has an Entra ID Premium P1 or P2 license.
+1. Verify that the Microsoft Graph Access Token was granted the `Reports.Read.All` permission.
+1. Verify that the authenticating user or the service principle of the application is in one of the following required administrative roles:
     - Reports Reader
     - Security Reader
     - Security Administrator
@@ -56,4 +57,4 @@ Example response
 
 ## More information
 
-If an application is configured with only the **AuditLog.Read.All** permission, this error may occur intermittently. This is expected behavior, as the **Directory.Read.All** permission is required to retrieve tenant licensing information when it isn't already cached. Ensure both permissions are included to avoid this issue.
+If an application is configured by using only the **AuditLog.Read.All** permission, this error might occur intermittently. This is expected behavior because the **Directory.Read.All** permission is required to retrieve tenant licensing information if it isn't already cached. To avoid this error, make sure that both permissions are included.