diff --git a/intune/configmgr/core/servers/deploy/configure/sql-server-alwayson-for-a-highly-available-site-database.md b/intune/configmgr/core/servers/deploy/configure/sql-server-alwayson-for-a-highly-available-site-database.md
index 01c56b01ea..ff17d4812f 100644
--- a/intune/configmgr/core/servers/deploy/configure/sql-server-alwayson-for-a-highly-available-site-database.md
+++ b/intune/configmgr/core/servers/deploy/configure/sql-server-alwayson-for-a-highly-available-site-database.md
@@ -300,7 +300,7 @@ The following limitations apply to all scenarios.
 
 ### Unsupported SQL Server options and configurations
 
-- **Basic availability groups**: Introduced with SQL Server 2016 Standard edition, basic availability groups don't support read access to secondary replicas. Configuration requires this access. For more information, see [Basic SQL Server availability groups](/sql/database-engine/availability-groups/windows/basic-availability-groups-always-on-availability-groups).
+- **Basic availability groups**: Introduced with SQL Server 2016 Standard edition, basic availability groups don't support read access to secondary replicas. Configuration Manager requires this access. For more information, see [Basic SQL Server availability groups](/sql/database-engine/availability-groups/windows/basic-availability-groups-always-on-availability-groups).
 
 - **Failover cluster instance**: Failover cluster instances aren't supported for a replica you use with Configuration Manager. For more information, see [SQL Server Always On failover cluster instances](/sql/sql-server/failover-clusters/windows/always-on-failover-cluster-instances-sql-server).