change back slashes to forward slashes

Author: cillroy

articles/active-directory-domain-services/active-directory-ds-check-health.md

@@ -29,7 +29,7 @@ Using the health page on your Azure portal, you are able to keep up-to-date on w
 3. In the left-hand navigation pane, click **Health**.
 
 The following picture illustrates a sample health page:
-![Example health page](.\media\active-directory-domain-services-alerts\health-page.png)
+![Example health page](./media/active-directory-domain-services-alerts/health-page.png)
 
 >[!NOTE]
 > Your managed domain's health is evaluated every hour. After making changes to your managed domain, wait until the next evaluation cycle to view your managed domain's updated health. The "Last evaluated" timestamp in the top right corner shows when the health of your managed domain was last evaluated.
@@ -40,10 +40,10 @@ The status in the top right of your health page indicates the overall health of
 
 | Status | Icon | Explanation |
 | --- | :----: | --- |
-| Running | <img src= ".\media\active-directory-domain-services-alerts\running-icon.png" width = "15"> | Your managed domain is running smoothly and does not have any critical or warning alerts. This domain may have informational alerts. |
-| Needs attention (Warning) | <img src= ".\media\active-directory-domain-services-alerts\warning-icon.png" width = "15"> | There are no critical alerts on your managed domain, but there are one or more warning alerts that need to be addressed. |
-| Needs attention (Critical) | <img src= ".\media\active-directory-domain-services-alerts\critical-icon.png" width = "15"> | There are one or more critical alerts on your managed domain. You may also have warning and/or informational alerts. |
-| Deploying | <img src= ".\media\active-directory-domain-services-alerts\deploying-icon.png" width = "15"> | Your domain is in the process of being deployed. |
+| Running | <img src= "./media/active-directory-domain-services-alerts/running-icon.png" width = "15"> | Your managed domain is running smoothly and does not have any critical or warning alerts. This domain may have informational alerts. |
+| Needs attention (Warning) | <img src= "./media/active-directory-domain-services-alerts/warning-icon.png" width = "15"> | There are no critical alerts on your managed domain, but there are one or more warning alerts that need to be addressed. |
+| Needs attention (Critical) | <img src= "./media/active-directory-domain-services-alerts/critical-icon.png" width = "15"> | There are one or more critical alerts on your managed domain. You may also have warning and/or informational alerts. |
+| Deploying | <img src= "./media/active-directory-domain-services-alerts/deploying-icon.png" width = "15"> | Your domain is in the process of being deployed. |
 
 ## Monitors
 Monitors are aspects of your managed domain that Azure AD Domain Services monitors on a regular basis. The best way to keep your monitors in a healthy state is to resolve any active alerts for your managed domain.

articles/active-directory-domain-services/active-directory-ds-mismatched-tenant-error.md

@@ -21,7 +21,7 @@ ms.author: ergreenl
 # Resolve mismatched directory errors for existing Azure AD Domain Services managed domains
 You have an existing Azure AD Domain Services managed domain. When you navigate to the Azure portal and view the managed domain, you see the following error message:
 
-![Mismatched directory error](.\media\getting-started\mismatched-tenant-error.png)
+![Mismatched directory error](./media/getting-started/mismatched-tenant-error.png)
 
 You cannot administer this managed domain until the error is resolved.
 

articles/active-directory-domain-services/active-directory-ds-networking.md

@@ -98,7 +98,7 @@ The following table illustrates a sample NSG you can configure for a virtual net
 
 Additionally, the NSG also illustrates how to lock down secure LDAP access over the internet. Skip this rule if you have not enabled secure LDAP access to your managed domain over the internet. The NSG contains a set of rules that allow inbound LDAPS access over TCP port 636 only from a specified set of IP addresses. The NSG rule to allow LDAPS access over the internet from specified IP addresses has a higher priority than the DenyAll NSG rule.
 
-![Sample NSG to secure LDAPS access over the internet](.\media\active-directory-domain-services-alerts\default-nsg.png)
+![Sample NSG to secure LDAPS access over the internet](./media/active-directory-domain-services-alerts/default-nsg.png)
 
 **More information** - [Create a Network Security Group](../virtual-network/manage-network-security-group.md).
 

articles/active-directory-domain-services/active-directory-ds-notifications.md

@@ -37,7 +37,7 @@ On the page it lists out all of the email recipients for email notifications for
 
 The following picture is an example of an email notification:
 
-![Example email notification](.\media\active-directory-domain-services-alerts\email-alert.png)
+![Example email notification](./media/active-directory-domain-services-alerts/email-alert.png)
 
 The email specifies the managed domain that the alert is present on, as well as giving the time of detection and a link to the Azure AD Domain Services health page in the Azure portal.
 

articles/active-directory-domain-services/active-directory-ds-suspension.md

@@ -24,7 +24,7 @@ When Azure Active Directory Domain Services (Azure AD DS) is unable to service a
 
 ## States your managed domain can be in
 
-![Suspended domain timeline](media\active-directory-domain-services-suspension\suspension-timeline.PNG)
+![Suspended domain timeline](media/active-directory-domain-services-suspension/suspension-timeline.PNG)
 
 The preceding graphic outlines the possible states an Azure AD DS managed domain can be in.
 

articles/active-directory-domain-services/active-directory-ds-troubleshoot-nsg.md

@@ -38,7 +38,7 @@ Invalid NSG configurations are the most common cause of network errors for Azure
 ## Sample NSG
 The following table depicts a sample NSG that would keep your managed domain secure while allowing Microsoft to monitor, manage, and update information.
 
-![sample NSG](.\media\active-directory-domain-services-alerts\default-nsg.png)
+![sample NSG](./media/active-directory-domain-services-alerts/default-nsg.png)
 
 >[!NOTE]
 > Azure AD Domain Services requires unrestricted outbound access from the virtual network. We recommend not to create any additional NSG rule that restricts outbound access for the virtual network.

articles/active-directory/hybrid/how-to-connect-adconnectivitytools.md

@@ -36,7 +36,7 @@ On the **Connect your directories** page, in the Azure AD Connect Wizard, if a n
 Whenever any of these issues are found, a related error message is displayed in the AADConnect Wizard:
 
 
-![Error](media\how-to-connect-adconnectivitytools\error1.png)
+![Error](media/how-to-connect-adconnectivitytools/error1.png)
 
 For example, when we are attempting to add a directory on the **Connect your directories** screen, Azure AD Connect needs to verify this and expects to be able to communicate with a domain controller over port 389.  If it cannot, we will see the error that is shown in the screenshot above.  
 

articles/active-directory/hybrid/tshoot-connect-objectsync.md

@@ -31,14 +31,14 @@ To run the troubleshooting task in the wizard, perform the following steps:
 4.	Navigate to the Additional Tasks page, select Troubleshoot, and click Next.
 5.	On the Troubleshooting page, click Launch to start the troubleshooting menu in PowerShell.
 6.	In the main menu, select Troubleshoot Object Synchronization.
-![](media\tshoot-connect-objectsync\objsynch11.png)
+![](media/tshoot-connect-objectsync/objsynch11.png)
 
 ### Troubleshooting Input Parameters
 The following input parameters are needed by the troubleshooting task:
 1.	**Object Distinguished Name** – This is the distinguished name of the object that needs troubleshooting
 2.	**AD Connector Name** – This is the name of the AD forest where the above object resides.
 3.	Azure AD tenant global administrator credentials
-![](media\tshoot-connect-objectsync\objsynch1.png)
+![](media/tshoot-connect-objectsync/objsynch1.png)
 
 ### Understand the results of the troubleshooting task
 The troubleshooting task performs the following checks:
@@ -55,27 +55,27 @@ The rest of this section describes specific results that are returned by the tas
 ### UPN Suffix is NOT verified with Azure AD Tenant
 When UserPrincipalName (UPN)/Alternate Login ID suffix is not verified with the Azure AD Tenant, then Azure Active Directory replaces the UPN suffixes with the default domain name "onmicrosoft.com".
 
-![](media\tshoot-connect-objectsync\objsynch2.png)
+![](media/tshoot-connect-objectsync/objsynch2.png)
 
 ### Changing UPN Suffix from one federated domain to another federated domain
 Azure Active Directory does not allow the synchronization of UserPrincipalName (UPN)/Alternate Login ID suffix change from one federated domain to another federated domain. This applies to domains, that are verified with the Azure AD Tenant and have the Authentication Type as Federated.
 
-![](media\tshoot-connect-objectsync\objsynch3.png) 
+![](media/tshoot-connect-objectsync/objsynch3.png) 
 
 ### Azure AD Tenant DirSync Feature ‘SynchronizeUpnForManagedUsers’ is disabled
 When the Azure AD Tenant DirSync Feature ‘SynchronizeUpnForManagedUsers’ is disabled, Azure Active Directory does not allow synchronization updates to UserPrincipalName/Alternate Login ID for licensed user accounts with managed authentication.
 
-![](media\tshoot-connect-objectsync\objsynch4.png)
+![](media/tshoot-connect-objectsync/objsynch4.png)
 
 ## Object is filtered due to domain filtering
 ### Domain is not configured to sync
 Object is out of scope due to domain not being configured. In the example below, the object is out of sync scope as the domain that it belongs to is filtered from synchronization.
 
-![](media\tshoot-connect-objectsync\objsynch5.png)
+![](media/tshoot-connect-objectsync/objsynch5.png)
 
 ### Domain is configured to sync but is missing run profiles/run steps
 Object is out of scope as the domain is missing run profiles/run steps. In the example below, the object is out of sync scope as the domain that it belongs to is missing run steps for the Full Import run profile.
-![](media\tshoot-connect-objectsync\objsynch6.png)
+![](media/tshoot-connect-objectsync/objsynch6.png)
 
 ## Object is filtered due to OU filtering
 The object is out of sync scope due to OU filtering configuration. In the example below, the object belongs to OU=NoSync,DC=bvtadwbackdc,DC=com.  This OU is not included in sync scope.</br>
@@ -94,7 +94,7 @@ Due to various differences between on-premises Active Directory and Azure Active
 ## HTML Report
 In addition to analyzing the object, the troubleshooting task also generates an HTML report that has everything known about the object. This HTML report can be shared with support team to do further troubleshooting, if needed.
 
-![](media\tshoot-connect-objectsync\objsynch8.png)
+![](media/tshoot-connect-objectsync/objsynch8.png)
 
 ## Next steps
 Learn more about [Integrating your on-premises identities with Azure Active Directory](whatis-hybrid-identity.md).

articles/active-directory/saas-apps/sharepoint-on-premises-tutorial.md

@@ -72,7 +72,7 @@ To configure the integration of SharePoint on-premises into Azure AD, you need t
 
 4. In the search box, type **SharePoint on-premises**, select **SharePoint on-premises** from result panel then click **Add** button to add the application.
 
-	![SharePoint on-premises in the results list](./media\sharepoint-on-premises-tutorial/tutorial_sharepointonpremises_addfromgallery.png)
+	![SharePoint on-premises in the results list](./media/sharepoint-on-premises-tutorial/tutorial_sharepointonpremises_addfromgallery.png)
 
 ## Configure and test Azure AD single sign-on
 
@@ -100,11 +100,11 @@ In this section, you enable Azure AD single sign-on in the Azure portal and conf
 
 2. On the **Single sign-on** dialog, select **Mode** as	**SAML-based Sign-on** to enable single sign-on.
 
-	![Single sign-on dialog box](./media\sharepoint-on-premises-tutorial/tutorial_sharepointonpremises_samlbase.png)
+	![Single sign-on dialog box](./media/sharepoint-on-premises-tutorial/tutorial_sharepointonpremises_samlbase.png)
 
 3. On the **SharePoint on-premises Domain and URLs** section, perform the following steps:
 
-	![SharePoint on-premises Domain and URLs single sign-on information](./media\sharepoint-on-premises-tutorial/tutorial_sharepointonpremises_url1.png)
+	![SharePoint on-premises Domain and URLs single sign-on information](./media/sharepoint-on-premises-tutorial/tutorial_sharepointonpremises_url1.png)
 
 	a. In the **Sign-on URL** textbox, type a URL using the following pattern: `https://<YourSharePointServerURL>/_trust/default.aspx`
 
@@ -114,21 +114,21 @@ In this section, you enable Azure AD single sign-on in the Azure portal and conf
 
 4. On the **SAML Signing Certificate** section, click **Certificate (Base64)** and then save the certificate file on your computer.
 
-	![The Certificate download link](./media\sharepoint-on-premises-tutorial/tutorial_sharepointonpremises_certificate.png)
+	![The Certificate download link](./media/sharepoint-on-premises-tutorial/tutorial_sharepointonpremises_certificate.png)
 
 	> [!Note]
 	> Please note down the file path to which you have downloaded the certificate file, as you need to use it later in the PowerShell script for configuration.
 
 5. Click **Save** button.
 
-	![Configure Single Sign-On Save button](./media\sharepoint-on-premises-tutorial/tutorial_general_400.png)
+	![Configure Single Sign-On Save button](./media/sharepoint-on-premises-tutorial/tutorial_general_400.png)
 
 6. On the **SharePoint on-premises Configuration** section, click **Configure SharePoint on-premises** to open **Configure sign-on** window. Copy the **SAML Entity ID** from the **Quick Reference section.** For **Single Sign-On Service URL**, use a value of the following pattern: `https://login.microsoftonline.com/_my_directory_id_/wsfed` 
 
     > [!Note]
     > _my_directory_id_ is the tenant id of Azure Ad subscription.
 
-	![SharePoint on-premises Configuration](./media\sharepoint-on-premises-tutorial/tutorial_sharepointonpremises_configure.png)
+	![SharePoint on-premises Configuration](./media/sharepoint-on-premises-tutorial/tutorial_sharepointonpremises_configure.png)
 
 	> [!NOTE]
 	> Sharepoint On-Premises application uses SAML 1.1 token, so Azure AD expects WS Fed request from SharePoint server and after authentication, it issues the SAML 1.1. token.
@@ -167,7 +167,7 @@ In this section, you enable Azure AD single sign-on in the Azure portal and conf
 
 	e. Click **OK**.
 
-	![Configuring your authentication provider](./media\sharepoint-on-premises-tutorial/fig10-configauthprovider.png)
+	![Configuring your authentication provider](./media/sharepoint-on-premises-tutorial/fig10-configauthprovider.png)
 
 	> [!NOTE]
 	> Some of the external users will not able to use this single sign-on integration as their UPN will have mangled value something like `MYEMAIL_outlook.com#ext#@TENANT.onmicrosoft.com`. Soon we will allow customers app config on how to handle the UPN depending on the user type. After that all your guest users should be able to use SSO seamlessly as the organization employees.
@@ -182,19 +182,19 @@ The objective of this section is to create a test user in the Azure portal calle
 
 1. In the Azure portal, in the left pane, click the **Azure Active Directory** button.
 
-    ![The Azure Active Directory button](./media\sharepoint-on-premises-tutorial/create_aaduser_01.png)
+    ![The Azure Active Directory button](./media/sharepoint-on-premises-tutorial/create_aaduser_01.png)
 
 2. To display the list of users, go to **Users and groups**, and then click **All users**.
 
-    ![The "Users and groups" and "All users" links](./media\sharepoint-on-premises-tutorial/create_aaduser_02.png)
+    ![The "Users and groups" and "All users" links](./media/sharepoint-on-premises-tutorial/create_aaduser_02.png)
 
 3. To open the **User** dialog box, click **Add** at the top of the **All Users** dialog box.
 
-    ![The Add button](./media\sharepoint-on-premises-tutorial/create_aaduser_03.png)
+    ![The Add button](./media/sharepoint-on-premises-tutorial/create_aaduser_03.png)
 
 4. In the **User** dialog box, perform the following steps:
 
-    ![The User dialog box](./media\sharepoint-on-premises-tutorial/create_aaduser_04.png)
+    ![The User dialog box](./media/sharepoint-on-premises-tutorial/create_aaduser_04.png)
 
     a. In the **Name** box, type **BrittaSimon**.
 
@@ -216,7 +216,7 @@ The users who will log into Azure AD and access SharePoint must be granted acces
 
 4. In Policy for Web Application, click **Add Users**.
 
-	![Searching for a user by their name claim](./media\sharepoint-on-premises-tutorial/fig11-searchbynameclaim.png)
+	![Searching for a user by their name claim](./media/sharepoint-on-premises-tutorial/fig11-searchbynameclaim.png)
 
 5. In the **Add Users** dialog box, click the appropriate zone in **Zones**, and then click **Next**.
 
@@ -228,7 +228,7 @@ The users who will log into Azure AD and access SharePoint must be granted acces
 
 9. In Permissions, click **Full Control**.
 
-	![Granting full control to a claims user](./media\sharepoint-on-premises-tutorial/fig12-grantfullcontrol.png)
+	![Granting full control to a claims user](./media/sharepoint-on-premises-tutorial/fig12-grantfullcontrol.png)
 
 10. Click **Finish**, and then click **OK**.
 
@@ -259,7 +259,7 @@ The configuration works for a single web application, but needs additional confi
 
 Users can now log into SharePoint 2016 using identities from Azure AD, but there are still opportunities for improvement to the user experience. For instance, searching for a user presents multiple search results in the people picker. There is a search result for each of the 3 claim types that were created in the claim mapping. To choose a user using the people picker, you must type their user name exactly and choose the **name** claim result.
 
-![Claims search results](./media\sharepoint-on-premises-tutorial/fig16-claimssearchresults.png)
+![Claims search results](./media/sharepoint-on-premises-tutorial/fig16-claimssearchresults.png)
 
 There is no validation on the values you search for, which can lead to misspellings or users accidentally choosing the wrong claim type to assign such as the **SurName** claim. This can prevent users from successfully accessing resources.
 
@@ -279,7 +279,7 @@ In this section, you enable Britta Simon to use Azure single sign-on by granting
 
 2. In the applications list, select **SharePoint on-premises**.
 
-	![The SharePoint link in the Applications list](./media\sharepoint-on-premises-tutorial/tutorial_sharepointonpremises_app.png)
+	![The SharePoint link in the Applications list](./media/sharepoint-on-premises-tutorial/tutorial_sharepointonpremises_app.png)
 
 3. In the menu on the left, click **Users and groups**.
 

articles/application-insights/app-insights-java-quick-start.md

@@ -125,7 +125,7 @@ Application Insights can gather telemetry data from any internet-connected appli
 
    ![Server metrics graphs](./media/app-insights-java-quick-start/livemetricsjava.png)
 
-To learn more about monitoring Java, check out the [additional App Insights Java documentation](.\app-insights-java-get-started.md).
+To learn more about monitoring Java, check out the [additional App Insights Java documentation](./app-insights-java-get-started.md).
 
 ## Clean up resources