fixing things

Author: MashaMSFT

articles/azure-sql/database/aad-authentication-overview.md

@@ -63,7 +63,7 @@ For more information on Azure AD hybrid identities, the setup, and synchronizati
 
 - Password hash authentication - [Implement password hash synchronization with Azure AD Connect sync](../../active-directory/hybrid/how-to-connect-password-hash-synchronization.md)
 - Pass-through authentication - [Azure Active Directory Pass-through Authentication](../../active-directory/hybrid/how-to-connect-pta-quick-start.md)
-- Federated authentication - [Deploying Active Directory Federation Services in Azure](/windows-server/identity/ad-fs/deployment/how-to-connect-fed-azure-adfs) and [Azure AD Connect and federation](../active-directory/hybrid/how-to-connect-fed-whatis.md)
+- Federated authentication - [Deploying Active Directory Federation Services in Azure](/windows-server/identity/ad-fs/deployment/how-to-connect-fed-azure-adfs) and [Azure AD Connect and federation](../../active-directory/hybrid/how-to-connect-fed-whatis.md)
 
 For a sample federated authentication with ADFS infrastructure (or user/password for Windows credentials), see the diagram below. The arrows indicate communication pathways.
 
@@ -89,7 +89,7 @@ To create a contained database user in Azure SQL Database, SQL Managed Instance,
 
 - The following members of Azure AD can be provisioned for Azure SQL:
 
-  - Native members: A member created in Azure AD in the managed domain or in a customer domain. For more information, see [Add your own domain name to Azure AD](../active-directory/active-directory-domains-add-azure-portal.md).
+  - Native members: A member created in Azure AD in the managed domain or in a customer domain. For more information, see [Add your own domain name to Azure AD](../../active-directory/fundamentals/add-custom-domain.md).
   - Members of an Active Directory domain federated with Azure Active Directory on a managed domain configured for seamless single sign-on with pass-through or password hash authentication. For more information, see [Microsoft Azure now supports federation with Windows Server Active Directory](https://azure.microsoft.com/blog/windows-azure-now-supports-federation-with-windows-server-active-directory//) and [Azure Active Directory Seamless Single Sign-On](../../active-directory/hybrid/how-to-connect-sso.md).
   - Imported members from other Azure AD's who are native or federated domain members.
   - Active Directory groups created as security groups.
@@ -163,9 +163,9 @@ The following authentication methods are supported for Azure AD server principal
 
 <!--Image references-->
 
-[1]: ./media/sql-database-aad-authentication/1aad-auth-diagram.png
-[2]: ./media/sql-database-aad-authentication/2subscription-relationship.png
-[3]: ./media/sql-database-aad-authentication/3admin-structure.png
+
+
+
 [4]: ./media/sql-database-aad-authentication/4select-subscription.png
 [5]: ./media/sql-database-aad-authentication/5ad-settings-portal.png
 [6]: ./media/sql-database-aad-authentication/6edit-directory-select.png

articles/azure-sql/database/business-continuity-high-availability-disaster-recover-hadr-overview.md

@@ -123,7 +123,7 @@ If you are using active geo-replication or auto-failover groups as your recovery
 
 ### Perform a geo-restore
 
-If you are using the automated backups with geo-redundant storage (enabled by default), you can recover the database using [geo-restore](../../key-vault/general/disaster-recovery-guidance.md#recover-using-geo-restore). Recovery usually takes place within 12 hours - with data loss of up to one hour determined by when the last log backup was taken and replicated. Until the recovery completes, the database is unable to record any transactions or respond to any queries. Note, geo-restore only restores the database to the last available point in time.
+If you are using the automated backups with geo-redundant storage (enabled by default), you can recover the database using [geo-restore](disaster-recovery-guidance.md#recover-using-geo-restore). Recovery usually takes place within 12 hours - with data loss of up to one hour determined by when the last log backup was taken and replicated. Until the recovery completes, the database is unable to record any transactions or respond to any queries. Note, geo-restore only restores the database to the last available point in time.
 
 > [!NOTE]
 > If the data center comes back online before you switch your application over to the recovered database, you can cancel the recovery.