Merge pull request #46964 from MicrosoftDocs/master

7/18 PM Publish

Author: huypub

.openpublishing.redirection.json

@@ -739,11 +739,21 @@
             "redirect_url": "/azure/active-directory/managed-service-identity/howto-assign-access-portal",
             "redirect_document_id": true
         },
+        {
+            "source_path": "articles/active-directory/pp/msi-howto-assign-access-portal.md",
+            "redirect_url": "/azure/active-directory/managed-service-identity/howto-assign-access-portal",
+            "redirect_document_id": false
+        },
         {
             "source_path": "articles/active-directory/msi-howto-assign-access-powershell.md",
             "redirect_url": "/azure/active-directory/managed-service-identity/howto-assign-access-powershell",
             "redirect_document_id": true
         },
+        {
+            "source_path": "articles/active-directory/pp/msi-howto-assign-access-powershell.md",
+            "redirect_url": "/azure/active-directory/managed-service-identity/howto-assign-access-powershell",
+            "redirect_document_id": false
+        },
         {
             "source_path": "articles/active-directory/msi-how-to-use-vm-sdk.md",
             "redirect_url": "/azure/active-directory/managed-service-identity/how-to-use-vm-sdk",
@@ -779,6 +789,11 @@
             "redirect_url": "/azure/active-directory/managed-service-identity/qs-configure-portal-windows-vm",
             "redirect_document_id": true
         },
+        {
+            "source_path": "articles/active-directory/pp/msi-qs-configure-portal-windows-vm.md",
+            "redirect_url": "/azure/active-directory/managed-service-identity/qs-configure-portal-windows-vm",
+            "redirect_document_id": false
+        },
         {
             "source_path": "articles/active-directory/msi-qs-configure-portal-windows-vmss.md",
             "redirect_url": "/azure/active-directory/managed-service-identity/qs-configure-portal-windows-vmss",
@@ -789,6 +804,11 @@
             "redirect_url": "/azure/active-directory/managed-service-identity/qs-configure-powershell-windows-vm",
             "redirect_document_id": true
         },
+        {
+            "source_path": "articles/active-directory/pp/msi-qs-configure-powershell-windows-vm.md",
+            "redirect_url": "/azure/active-directory/managed-service-identity/qs-configure-powershell-windows-vm",
+            "redirect_document_id": false
+        },
         {
             "source_path": "articles/active-directory/msi-qs-configure-sdk-windows-vm.md",
             "redirect_url": "/azure/active-directory/managed-service-identity/qs-configure-sdk-windows-vm",
@@ -799,6 +819,11 @@
             "redirect_url": "/azure/active-directory/managed-service-identity/qs-configure-template-windows-vm",
             "redirect_document_id": true
         },
+        {
+            "source_path": "articles/active-directory/pp/msi-qs-configure-template-windows-vm.md",
+            "redirect_url": "/azure/active-directory/managed-service-identity/qs-configure-template-windows-vm",
+            "redirect_document_id": false
+        },
         {
             "source_path": "articles/active-directory/msi-qs-configure-template-windows-vmss.md",
             "redirect_url": "/azure/active-directory/managed-service-identity/qs-configure-template-windows-vmss",
@@ -814,16 +839,31 @@
             "redirect_url": "/azure/active-directory/managed-service-identity/tutorial-linux-vm-access-datalake",
             "redirect_document_id": true
         },
+        {
+            "source_path": "articles/active-directory/pp/msi-tutorial-linux-vm-access-datalake.md",
+            "redirect_url": "/azure/active-directory/managed-service-identity/tutorial-linux-vm-access-datalake",
+            "redirect_document_id": false
+        },
         {
             "source_path": "articles/active-directory/msi-tutorial-linux-vm-access-nonaad.md",
             "redirect_url": "/azure/active-directory/managed-service-identity/tutorial-linux-vm-access-nonaad",
             "redirect_document_id": true
         },
+        {
+            "source_path": "articles/active-directory/pp/msi-tutorial-linux-vm-access-nonaad.md",
+            "redirect_url": "/azure/active-directory/managed-service-identity/tutorial-linux-vm-access-nonaad",
+            "redirect_document_id": false
+        },
         {
             "source_path": "articles/active-directory/msi-tutorial-linux-vm-access-storage-sas.md",
             "redirect_url": "/azure/active-directory/managed-service-identity/tutorial-linux-vm-access-storage-sas",
             "redirect_document_id": false
         },
+        {
+            "source_path": "articles/active-directory/pp/msi-tutorial-linux-vm-access-storage-sas.md",
+            "redirect_url": "/azure/active-directory/managed-service-identity/tutorial-linux-vm-access-storage-sas",
+            "redirect_document_id": false
+        },
         {
             "source_path": "articles/active-directory/msi-tutorial-linux-vm-access-storage.md",
             "redirect_url": "/azure/active-directory/managed-service-identity/tutorial-linux-vm-access-storage",
@@ -834,31 +874,61 @@
             "redirect_url": "/azure/active-directory/managed-service-identity/tutorial-windows-vm-access-arm",
             "redirect_document_id": true
         },
+        {
+            "source_path": "articles/active-directory/pp/msi-tutorial-windows-vm-access-arm.md",
+            "redirect_url": "/azure/active-directory/managed-service-identity/tutorial-windows-vm-access-arm",
+            "redirect_document_id": false
+        },
         {
             "source_path": "articles/active-directory/msi-tutorial-windows-vm-access-datalake.md",
             "redirect_url": "/azure/active-directory/managed-service-identity/tutorial-windows-vm-access-datalake",
             "redirect_document_id": true
         },
+        {
+            "source_path": "articles/active-directory/pp/msi-tutorial-windows-vm-access-datalake.md",
+            "redirect_url": "/azure/active-directory/managed-service-identity/tutorial-windows-vm-access-datalake",
+            "redirect_document_id": false
+        },
         {
             "source_path": "articles/active-directory/msi-tutorial-windows-vm-access-nonaad.md",
             "redirect_url": "/azure/active-directory/managed-service-identity/tutorial-windows-vm-access-nonaad",
             "redirect_document_id": true
         },
+        {
+            "source_path": "articles/active-directory/pp/msi-tutorial-windows-vm-access-nonaad.md",
+            "redirect_url": "/azure/active-directory/managed-service-identity/tutorial-windows-vm-access-nonaad",
+            "redirect_document_id": false
+        },
         {
             "source_path": "articles/active-directory/msi-tutorial-windows-vm-access-sql.md",
             "redirect_url": "/azure/active-directory/managed-service-identity/tutorial-windows-vm-access-sql",
             "redirect_document_id": true
         },
+        {
+            "source_path": "articles/active-directory/pp/msi-tutorial-windows-vm-access-sql.md",
+            "redirect_url": "/azure/active-directory/managed-service-identity/tutorial-windows-vm-access-sql",
+            "redirect_document_id": false
+        },
         {
             "source_path": "articles/active-directory/msi-tutorial-windows-vm-access-storage-sas.md",
             "redirect_url": "/azure/active-directory/managed-service-identity/tutorial-windows-vm-access-storage-sas",
             "redirect_document_id": true
         },
+        {
+            "source_path": "articles/active-directory/pp/msi-tutorial-windows-vm-access-storage-sas.md",
+            "redirect_url": "/azure/active-directory/managed-service-identity/tutorial-windows-vm-access-storage-sas",
+            "redirect_document_id": false
+        },
         {
             "source_path": "articles/active-directory/msi-tutorial-windows-vm-access-storage.md",
             "redirect_url": "/azure/active-directory/managed-service-identity/tutorial-windows-vm-access-storage",
             "redirect_document_id": true
         },
+        {
+            "source_path": "articles/active-directory/pp/msi-tutorial-windows-vm-access-storage.md",
+            "redirect_url": "/azure/active-directory/managed-service-identity/tutorial-windows-vm-access-storage",
+            "redirect_document_id": false
+        },
         {
             "source_path": "articles/active-directory/active-directory-self-service-application-access.md",
             "redirect_url": "/azure/active-directory/application-access-self-service-how-to",
@@ -24817,7 +24887,12 @@
         },
         {
             "source_path": "articles/active-directory/pp/index.md",
-            "redirect_url": "/azure/active-directory/pp/msi-tutorial-linux-vm-access-storage",
+            "redirect_url": "/azure/active-directory/managed-service-identity/index",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "articles/active-directory/pp/msi-tutorial-linux-vm-access-storage.md",
+            "redirect_url": "/azure/active-directory/managed-service-identity/tutorial-linux-vm-access-storage",
             "redirect_document_id": false
         },
         {
@@ -26329,6 +26404,11 @@
             "source_path": "articles/hdinsight/kafka/apache-kafka-azure-functions.md",
             "redirect_url": "/azure/hdinsight/kafka/apache-kafka-introduction",
             "redirect_document_id": false
-        }     
+        },
+        {
+        "source_path": "articles/cognitive-services/LUIS/traffic-manager.md",
+        "redirect_url": "/azure/cognitive-services/LUIS/luis-traffic-manager",
+        "redirect_document_id": true
+        }       
     ]
 }

articles/active-directory/active-directory-tou.md

@@ -12,7 +12,7 @@ ms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: conceptual
 ms.component: compliance-reports
-ms.date: 06/29/2018
+ms.date: 07/18/2018
 ms.author: rolyon
 
 ---
@@ -82,7 +82,7 @@ Once you have finalized your Terms of use document, use the following procedure
 
     ![Add TOU](media/active-directory-tou/create-tou.png)
 
-## View who has accepted and declined
+## View report of who has accepted and declined
 The Terms of use blade shows a count of the users who have accepted and declined. These counts and who accepted/declined are stored for the life of the Terms of use.
 
 1. Sign in to Azure and navigate to **Terms of use** at [https://aka.ms/catou](https://aka.ms/catou).
@@ -93,10 +93,10 @@ The Terms of use blade shows a count of the users who have accepted and declined
 
     ![Audit Event](media/active-directory-tou/accepted-tou.png)
 
-## View audit logs
+## View Azure AD audit logs
 If you want to view additional activity, Azure AD Terms of use includes audit logs. Each user consent triggers an event in the audit logs that is stored for 30 days. You can view these logs in the portal or download as a .csv file.
 
-To get started with audit logs, use the following procedure:
+To get started with Azure AD audit logs, use the following procedure:
 
 1. Sign in to Azure and navigate to **Terms of use** at [https://aka.ms/catou](https://aka.ms/catou).
 
@@ -163,11 +163,20 @@ Conditional access policies take effect immediately. When this happens, the admi
 ## Frequently asked questions
 
 **Q: How do I see when/if a user has accepted a Terms of use?**</br>
-A: On the Terms of use blade, click the number under **Accepted**. You can also view or search the accept activity in the audit logs. For more information, see [View who has accepted and declined](#view-who-has-accepted-and-declined) and [View audit logs](#view-audit-logs).
+A: On the Terms of use blade, click the number under **Accepted**. You can also view or search the accept activity in the Azure AD audit logs. For more information, see [View report of who has accepted and declined](#view-who-has-accepted-and-declined) and [View Azure AD audit logs](#view-azure-ad-audit-logs).
+ 
+**Q: How long is information stored?**</br>
+A: The user counts in the Terms of use report and who accepted/declined are stored for the life of the Terms of use. The Azure AD audit logs are stored for 30 days.
 
-**Q: If you change the Terms of use terms, does it require users to accept again?**</br>
+**Q: Why do I see a different number of consents in the Terms of use report vs. the Azure AD audit logs?**</br>
+A: The Terms of use report is stored for the lifetime of that Terms of use, while the Azure AD audit logs are stored for 30 days. Also, the Terms of use report only displays the users current consent state. For example, if a user declines and then accepts, the Terms of use report will only show that user's accept. If you need to see the history, you can use the Azure AD audit logs.
+
+**Q: If I change the Terms of use terms, does it require users to accept again?**</br>
 A: Yes, an administrator can change the Terms of use terms and it requires users to reaccept the new terms.
 
+**Q: If hyperlinks are in the Terms of use PDF document, will end users be able to click them?**</br>
+A: The PDF is rendered by default as a JPEG, so hyperlinks are not clickable. Users have the option to select **Having trouble viewing? Click here**, which renders the PDF natively where hyperlinks are supported.
+
 **Q: Can a Terms of use support multiple languages?**</br>
 A: Yes.  Currently there are 18 different languages an administrator can configure for a single Terms of use. 
 
@@ -185,6 +194,7 @@ A: The user is blocked from getting access to the application. The user would ha
 
 **Q: Is it possible to unaccept Terms of use that were previously accepted?**</br>
 A: You can [review previously accepted Terms of use](#how-users-can-review-their-terms-of-use), but currently there isn't a way to unaccept.
- 
-**Q: How long is information stored?**</br>
-A: The user counts and who accepted/declined are stored for the life of the Terms of use. The audit logs are stored for 30 days.
+
+## Next steps
+
+- [Best practices for conditional access in Azure Active Directory](active-directory-conditional-access-best-practices.md)

articles/active-directory/device-management-faq.md

@@ -99,6 +99,11 @@ For down-level Windows OS versions that are on-premises AD domain-joined:
 
 ---
 
+**Q: How do I connect to a remote Azure AD joined device?**
+**A:** Refer to the article https://docs.microsoft.com/en-us/windows/client-management/connect-to-remote-aadj-pc for details.
+
+---
+
 **Q: Why do I see duplicate device entries in Azure portal?**
 
 **A:**

articles/active-directory/device-management-troubleshoot-hybrid-join-windows-legacy.md

@@ -53,6 +53,8 @@ This article provides you with troubleshooting guidance on how to resolve potent
 
 - A reinstallation of the operating system or manual re-registration may create a new registration in Azure AD, which results in multiple entries under the USER info tab in the Azure portal. 
 
+- Make sure [KB4284842](https://support.microsoft.com/en-us/help/4284842) is installed, in case of Windows 7 SP1 or Windows Server 2008 R2 SP1. This update prevents future authentication failures due to customer's access loss to protected keys after changing password.
+
 ## Step 1: Retrieve the registration status 
 
 **To verify the registration status:**  

articles/active-directory/fundamentals/whats-new.md

@@ -35,27 +35,27 @@ This page is updated monthly, so revisit it regularly.
 
 ## July 2018
 
-### New Azure AD email design and sender information - End of July
+### Improvements to Azure Active Directory email notifications
 
 **Type:** Plan for change  
 **Service category:** Other  
 **Product capability:** Identity lifecycle management
 
-At the **end of July 2018**, you'll notice that all Azure AD emails will have an updated design, sender email address, and sender display name when sent from the following services:
-
-- Azure AD Identity Protection
-- Azure AD Connect Health
-- Azure AD Provisioning Service
-- Azure AD Enterprise Application Management
+At the **end of July 2018**, Azure Active Directory (Azure AD) emails will feature an updated design, as well as changes to the sender email address and sender display name, when sent from the following services:
+ 
 - Azure AD Access Reviews
+- Azure AD Connect Health 
+- Azure AD Identity Protection 
 - Azure AD Privileged Identity Management
+- Enterprise App Expiring Certificate Notifications
+- Enterprise App Provisioning Service Notifications
+ 
+The email notifications will be sent from the following email address and display name:
 
-Also at that time, email notifications will start to use the following address:
-
-- Display name: Microsoft Azure
 - Email address: [email protected]
-
-For an example of some of the new e-mail designs, see [Email notifications in Azure AD PIM](https://go.microsoft.com/fwlink/?linkid=2005832).
+- Display name: Microsoft Azure
+ 
+For an example of some of the new e-mail designs and more information, see [Email notifications in Azure AD PIM](https://go.microsoft.com/fwlink/?linkid=2005832).
 
 ---