docs(vdc): documentation update 2026-05-23

docs/azure_backup_create_sql_process.md

@@ -3,7 +3,7 @@ title: "Step 5. Specify Policy Processing Settings"
 product: "vdc"
 doc_type: "userguide"
 source_url: "https://helpcenter.veeam.com/docs/vdc/userguide/azure_backup_create_sql_process.html"
-last_updated: "4/17/2026"
+last_updated: "5/22/2026"
 product_version: ""
 ---
 
@@ -32,9 +32,7 @@ To back up the selected databases without a staging server, do the following:
 
 For an account to be displayed in the Account list, it must be added to Veeam Data Cloud as described in section [Adding Database Account](azure_settings_accounts_database_add.md). If you have not added the necessary Azure SQL account beforehand, you can do it without closing the New Azure SQL Policy wizard. To add an account, click Add and complete the [New SQL server account wizard](azure_settings_accounts_database_add.md).
 
-* Entra ID Application — to use an Entra ID application.
-
-To enable Microsoft Entra ID authentication, the Azure SQL Server must have your [Azure Service Account](azure_settings_accounts_service_view.md) application ID configured as its Entra ID administrator. You can set the Entra ID administrator in the settings of the Azure SQL Server in the Azure portal. To learn more, see [Microsoft documentation](https://learn.microsoft.com/en-us/azure/azure-sql/database/authentication-aad-configure?view=azuresql&tabs=azure-portal).
+* Entra ID Application — to use an Entra ID application. Make sure that the Azure Service Account application is configured as the Entra ID administrator of the SQL Server, as described in [Configuring Entra ID Administrator](#entra_admin).
 
 1. Click Apply.
 
@@ -72,11 +70,21 @@ For an account to be displayed in the Account list, it must be added to Veeam Da
 | Important |
 | If the Azure SQL account you use to authenticate against the staging server does not have the sysadmin [server-level role](https://learn.microsoft.com/en-us/sql/relational-databases/security/authentication-access/server-level-roles?view=sql-server-ver16) assigned, you can only use the source SQL Server as a staging server — otherwise, the backup operation will fail. |
 
-* Entra ID Application — to use an Entra ID application.
-
-To enable Microsoft Entra ID authentication, the Azure SQL Server must have your [Azure Service Account](azure_settings_accounts_service_view.md) application ID configured as its Entra ID administrator. You can set the Entra ID administrator in the settings of the Azure SQL Server in the Azure portal. To learn more, see [Microsoft documentation](https://learn.microsoft.com/en-us/azure/azure-sql/database/authentication-aad-configure?view=azuresql&tabs=azure-portal).
+* Entra ID Application — to use an Entra ID application. Make sure that the Azure Service Account application is configured as the Entra ID administrator of the SQL Server, as described in [Configuring Entra ID Administrator](#entra_admin).
 
 1. Click Apply.
 
 [![Specify Policy Processing Settings](images/azure_backup_create_sql_process_staging.png)](images/azure_backup_create_sql_process_staging.png "Specify Policy Processing Settings")
 
+Configuring Entra ID Administrator
+
+To enable Microsoft Entra ID authentication, the Azure SQL Server must have an Entra ID administrator that grants access to your [Azure Service Account](azure_settings_accounts_service_view.md) application. You can do this in one of the following ways:
+
+* Assign the Azure Service Account application directly as the Entra ID administrator of the SQL Server.
+* Add the Azure Service Account application to a Microsoft Entra ID group, and assign that group as the Entra ID administrator of the SQL Server. Use this option if the SQL Server already has an administrator that you want to keep.
+
+|  |
+| --- |
+| Important |
+| The Entra ID administrator must be assigned through the Azure portal, as described in [Microsoft documentation](https://learn.microsoft.com/en-us/azure/azure-sql/database/authentication-aad-configure?view=azuresql&tabs=azure-portal). Any other assignment method is not supported and will cause backup operations to fail. |
+

docs/entra_id_properties.md

@@ -3,7 +3,7 @@ title: "Supported Entra ID Item Properties"
 product: "vdc"
 doc_type: "userguide"
 source_url: "https://helpcenter.veeam.com/docs/vdc/userguide/entra_id_properties.html"
-last_updated: "3/19/2026"
+last_updated: "5/22/2026"
 product_version: ""
 ---
 
@@ -15,7 +15,7 @@ Veeam Data Cloud for Microsoft Entra ID protects the following items:
 * Entra ID objects with their properties
 * Microsoft Intune policies with their properties
 * Entra ID audit logs
-* Entra ID sign-in logs
+* Entra ID interactive sign-in logs
 
 This article lists all supported properties for the items that Veeam Data Cloud for Microsoft Entra ID protects.
 

docs/entra_id_protection.md

@@ -3,7 +3,7 @@ title: "Microsoft Entra ID Protection"
 product: "vdc"
 doc_type: "userguide"
 source_url: "https://helpcenter.veeam.com/docs/vdc/userguide/entra_id_protection.html"
-last_updated: "3/19/2026"
+last_updated: "5/22/2026"
 product_version: ""
 ---
 
@@ -13,7 +13,7 @@ product_version: ""
 Veeam Data Cloud for Microsoft Entra ID is a backup as a service solution developed to deliver data protection and disaster recovery for Microsoft Entra ID. With Veeam Data Cloud for Microsoft Entra ID, you can perform the following operations:
 
 * Create backups of Microsoft Entra ID tenants.
-* Create backups of Microsoft Entra ID audit and sign-in logs.
+* Create backups of Microsoft Entra ID audit and interactive sign-in logs.
 * Restore users, groups, administrative units, roles, applications, service principals, Conditional Access policies and Microsoft Intune policies from Microsoft Entra ID tenant backups to the Microsoft Entra ID environment.
 * Restore properties of users, groups, administrative units, roles, applications, service principals, Conditional Access policies and Microsoft Intune policies from Microsoft Entra ID tenant backups to the Microsoft Entra ID environment.
 * Export audit and sign-in logs from Microsoft Entra ID log backups.

docs/m365_dashboard.md

@@ -3,7 +3,7 @@ title: "Viewing Dashboard"
 product: "vdc"
 doc_type: "userguide"
 source_url: "https://helpcenter.veeam.com/docs/vdc/userguide/m365_dashboard.html"
-last_updated: "5/12/2026"
+last_updated: "5/22/2026"
 product_version: ""
 ---
 
@@ -36,7 +36,7 @@ The Dashboard page displays the following sections:
 | Veeam Data Cloud calculates the number of unprotected accounts according to the following rules. During the initial backup session, Veeam Data Cloud creates the first restore point that contains all objects included in the backup policy. During subsequent backup sessions, Veeam Data Cloud creates restore points that contain objects for which a new version appeared in Microsoft 365 since the previous backup session. If a restore point that contains the object has not been created within the last 31 days, the object will be considered an unprotected account. For more information, see [Backup Retention](m365_data_backup.md#retention) and [License Consumption](m365_licensing.md#consumption). |
 
 * The Backup Storage section provides information about the total storage used by all the backups each month.
-* The License Activity section provides information about the Veeam Data Cloud licensed users in the last 7, 30 or 90 days.
+* The License Activity section provides information about active users from your Microsoft 365 tenancy in the last 7, 30 or 90 days. Active and inactive users both consume Microsoft 365 licenses, however, inactive users are users who have not used any Microsoft 365 apps during the specified period.
 * The Microsoft 365 Storage Use section provides information about the tenant repository storage usage.
 
 |  |

docs/provider/azure_backup_create_sql_process.md

@@ -3,7 +3,7 @@ title: "Step 5. Specify Policy Processing Settings"
 product: "vdc"
 doc_type: "provider"
 source_url: "https://helpcenter.veeam.com/docs/vdc/provider/azure_backup_create_sql_process.html"
-last_updated: "4/17/2026"
+last_updated: "5/22/2026"
 product_version: ""
 ---
 
@@ -32,9 +32,7 @@ To back up the selected databases without a staging server, do the following:
 
 For an account to be displayed in the Account list, it must be added to Veeam Data Cloud as described in section [Adding Database Account](azure_settings_accounts_database_add.md). If you have not added the necessary Azure SQL account beforehand, you can do it without closing the New Azure SQL Policy wizard. To add an account, click Add and complete the [New SQL server account wizard](azure_settings_accounts_database_add.md).
 
-* Entra ID Application — to use an Entra ID application.
-
-To enable Microsoft Entra ID authentication, the Azure SQL Server must have your [Azure Service Account](azure_settings_accounts_service_view.md) application ID configured as its Entra ID administrator. You can set the Entra ID administrator in the settings of the Azure SQL Server in the Azure portal. To learn more, see [Microsoft documentation](https://learn.microsoft.com/en-us/azure/azure-sql/database/authentication-aad-configure?view=azuresql&tabs=azure-portal).
+* Entra ID Application — to use an Entra ID application. Make sure that the Azure Service Account application is configured as the Entra ID administrator of the SQL Server, as described in [Configuring Entra ID Administrator](#entra_admin).
 
 1. Click Apply.
 
@@ -72,11 +70,21 @@ For an account to be displayed in the Account list, it must be added to Veeam Da
 | Important |
 | If the Azure SQL account you use to authenticate against the staging server does not have the sysadmin [server-level role](https://learn.microsoft.com/en-us/sql/relational-databases/security/authentication-access/server-level-roles?view=sql-server-ver16) assigned, you can only use the source SQL Server as a staging server — otherwise, the backup operation will fail. |
 
-* Entra ID Application — to use an Entra ID application.
-
-To enable Microsoft Entra ID authentication, the Azure SQL Server must have your [Azure Service Account](azure_settings_accounts_service_view.md) application ID configured as its Entra ID administrator. You can set the Entra ID administrator in the settings of the Azure SQL Server in the Azure portal. To learn more, see [Microsoft documentation](https://learn.microsoft.com/en-us/azure/azure-sql/database/authentication-aad-configure?view=azuresql&tabs=azure-portal).
+* Entra ID Application — to use an Entra ID application. Make sure that the Azure Service Account application is configured as the Entra ID administrator of the SQL Server, as described in [Configuring Entra ID Administrator](#entra_admin).
 
 1. Click Apply.
 
 [![Specify Policy Processing Settings](images/azure_backup_create_sql_process_staging.webp)](images/azure_backup_create_sql_process_staging.webp "Specify Policy Processing Settings")
 
+Configuring Entra ID Administrator
+
+To enable Microsoft Entra ID authentication, the Azure SQL Server must have an Entra ID administrator that grants access to your [Azure Service Account](azure_settings_accounts_service_view.md) application. You can do this in one of the following ways:
+
+* Assign the Azure Service Account application directly as the Entra ID administrator of the SQL Server.
+* Add the Azure Service Account application to a Microsoft Entra ID group, and assign that group as the Entra ID administrator of the SQL Server. Use this option if the SQL Server already has an administrator that you want to keep.
+
+|  |
+| --- |
+| Important |
+| The Entra ID administrator must be assigned through the Azure portal, as described in [Microsoft documentation](https://learn.microsoft.com/en-us/azure/azure-sql/database/authentication-aad-configure?view=azuresql&tabs=azure-portal). Any other assignment method is not supported and will cause backup operations to fail. |
+

docs/provider/entra_id_properties.md

@@ -3,7 +3,7 @@ title: "Supported Entra ID Item Properties"
 product: "vdc"
 doc_type: "provider"
 source_url: "https://helpcenter.veeam.com/docs/vdc/provider/entra_id_properties.html"
-last_updated: "3/19/2026"
+last_updated: "5/22/2026"
 product_version: ""
 ---
 
@@ -15,7 +15,7 @@ Veeam Data Cloud for Microsoft Entra ID protects the following items:
 * Entra ID objects with their properties
 * Microsoft Intune policies with their properties
 * Entra ID audit logs
-* Entra ID sign-in logs
+* Entra ID interactive sign-in logs
 
 This article lists all supported properties for the items that Veeam Data Cloud for Microsoft Entra ID protects.
 

docs/provider/entra_id_protection.md

@@ -3,7 +3,7 @@ title: "Microsoft Entra ID Protection"
 product: "vdc"
 doc_type: "provider"
 source_url: "https://helpcenter.veeam.com/docs/vdc/provider/entra_id_protection.html"
-last_updated: "3/19/2026"
+last_updated: "5/22/2026"
 product_version: ""
 ---
 
@@ -13,7 +13,7 @@ product_version: ""
 Veeam Data Cloud for Microsoft Entra ID is a backup as a service solution developed to deliver data protection and disaster recovery for Microsoft Entra ID. With Veeam Data Cloud for Microsoft Entra ID, you can perform the following operations:
 
 * Create backups of Microsoft Entra ID tenants.
-* Create backups of Microsoft Entra ID audit and sign-in logs.
+* Create backups of Microsoft Entra ID audit and interactive sign-in logs.
 * Restore users, groups, administrative units, roles, applications, service principals, Conditional Access policies and Microsoft Intune policies from Microsoft Entra ID tenant backups to the Microsoft Entra ID environment.
 * Restore properties of users, groups, administrative units, roles, applications, service principals, Conditional Access policies and Microsoft Intune policies from Microsoft Entra ID tenant backups to the Microsoft Entra ID environment.
 * Export audit and sign-in logs from Microsoft Entra ID log backups.

docs/provider/m365_dashboard.md

@@ -3,7 +3,7 @@ title: "Viewing Dashboard"
 product: "vdc"
 doc_type: "provider"
 source_url: "https://helpcenter.veeam.com/docs/vdc/provider/m365_dashboard.html"
-last_updated: "5/12/2026"
+last_updated: "5/22/2026"
 product_version: ""
 ---
 
@@ -36,7 +36,7 @@ The Dashboard page displays the following sections:
 | Veeam Data Cloud calculates the number of unprotected accounts according to the following rules. During the initial backup session, Veeam Data Cloud creates the first restore point that contains all objects included in the backup policy. During subsequent backup sessions, Veeam Data Cloud creates restore points that contain objects for which a new version appeared in Microsoft 365 since the previous backup session. If a restore point that contains the object has not been created within the last 31 days, the object will be considered an unprotected account. For more information, see [Backup Retention](m365_data_backup.md#retention) and [License Consumption](m365_licensing.md#consumption). |
 
 * The Backup Storage section provides information about the total storage used by all the backups each month.
-* The License Activity section provides information about the Veeam Data Cloud licensed users in the last 7, 30 or 90 days.
+* The License Activity section provides information about active users from your Microsoft 365 tenancy in the last 7, 30 or 90 days. Active and inactive users both consume Microsoft 365 licenses, however, inactive users are users who have not used any Microsoft 365 apps during the specified period.
 * The Microsoft 365 Storage Use section provides information about the tenant repository storage usage.
 
 |  |