Alt texts

Author: yoelhor

articles/active-directory/governance/entitlement-management-overview.md

@@ -85,7 +85,7 @@ With an access package, an administrator or delegated access package manager lis
 
 Access packages also include one or more *policies*. A policy defines the rules or guardrails for assignment to access package. Each policy can be used to ensure that only the appropriate users are able to have access assignments, and the access is time-limited and will expire if not renewed.
 
-![Access package and policies](./media/entitlement-management-overview/elm-overview-access-package.png)
+![Diagram of access package and policies.](./media/entitlement-management-overview/elm-overview-access-package.png)
 
 You can have policies for users to request access. In these kinds of policies, an administrator or access package manager defines
 
@@ -100,7 +100,7 @@ The following diagram shows an example of the different elements in entitlement
 - **Access package 1** includes a single group as a resource. Access is defined with a policy that enables a set of users in the directory to request access.
 - **Access package 2** includes a group, an application, and a SharePoint Online site as resources. Access is defined with two different policies. The first policy enables a set of users in the directory to request access. The second policy enables users in an external directory to request access.
 
-![Entitlement management overview](./media/entitlement-management-overview/elm-overview.png)
+![Entitlement management overview diagram](./media/entitlement-management-overview/elm-overview.png)
 
 ## When should I use access packages?
 

articles/active-directory/governance/what-is-identity-lifecycle-management.md

@@ -19,7 +19,7 @@ Identity Governance helps organizations achieve a balance between productivity.
 
 **Identity lifecycle management** is the foundation for Identity Governance, and effective governance at scale requires modernizing the identity lifecycle management infrastructure for applications. Identity Lifecycle Management aims to automate and manage the entire digital identity lifecycle process. 
 
-![cloud provisioning](media/what-is-provisioning/cloud-1.png)
+![Diagram of the cloud provisioning](media/what-is-provisioning/cloud-1.png)
 
 ## What is a digital identity?
 

articles/active-directory/governance/what-is-provisioning.md

@@ -27,11 +27,11 @@ Azure AD currently provides three areas of automated provisioning.  They are:
 - Provisioning from Azure AD to applications, via **[App provisioning](#app-provisioning)**  
 - Provisioning between Azure AD and Active Directory domain services, via **[inter-directory provisioning](#inter-directory-provisioning)** 
 
-![identity lifecycle management](media/what-is-provisioning/provisioning.png)
+![Diagram of the identity lifecycle management.](media/what-is-provisioning/provisioning.png)
 
 ## HR-driven provisioning
 
-![HR provisioning](media/what-is-provisioning/cloud-2a.png)
+![Diagram of the HR provisioning.](media/what-is-provisioning/cloud-2a.png)
 
 Provisioning from HR to Azure AD involves the creation of objects, typically user identities representing each employee, but in some cases other objects representing departments or other structures, based on the information that is in your HR system.  
 
@@ -52,15 +52,15 @@ For more information, see [What is HR driven provisioning?](../app-provisioning/
 
 ## App provisioning
 
-![app provisioning](media/what-is-provisioning/cloud-3b.png)
+![Diagram that shows the app provisioning flow.](media/what-is-provisioning/cloud-3b.png)
 
 In Azure AD, the term **[app provisioning](../app-provisioning/user-provisioning.md)** refers to automatically creating copies of user identities in the applications that users need access to, for applications that have their own data store, distinct from Azure AD or Active Directory. In addition to creating user identities, app provisioning includes the maintenance and removal of user identities from those apps, as the user's status or roles change. Common scenarios include provisioning an Azure AD user into applications like [Dropbox](../saas-apps/dropboxforbusiness-provisioning-tutorial.md), [Salesforce](../saas-apps/salesforce-provisioning-tutorial.md), [ServiceNow](../saas-apps/servicenow-provisioning-tutorial.md), as each of these applications have their own user repository distinct from Azure AD.
 
 For more information, see [What is app provisioning?](../app-provisioning/user-provisioning.md)
 
 ## Inter-directory provisioning
 
-![inter-directory provisioning](media/what-is-provisioning/cloud-4a.png)
+![Diagram that shows the inter-directory provisioning](media/what-is-provisioning/cloud-4a.png)
 
 Many organizations rely upon both Active Directory and Azure AD, and may have applications connected to Active Directory, such as on-premises file servers.