From e04b6d97bbf177377995e143a00d53b63005de07 Mon Sep 17 00:00:00 2001 From: Daniel Simpson Date: Tue, 28 Jul 2020 17:44:50 -0700 Subject: [PATCH] fixing broken bookmarks --- .../portal-submission-troubleshooting.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/windows/security/threat-protection/intelligence/portal-submission-troubleshooting.md b/windows/security/threat-protection/intelligence/portal-submission-troubleshooting.md index 6de66641a7..b5385f6f5b 100644 --- a/windows/security/threat-protection/intelligence/portal-submission-troubleshooting.md +++ b/windows/security/threat-protection/intelligence/portal-submission-troubleshooting.md @@ -34,18 +34,18 @@ This process requires a global or application admin in the tenant. ![grant consent image](images/msi-grant-admin-consent.jpg) - 4. If the administrator receives an error while attempting to provide consent manually, try either [Option 1](#Option-1:-Approve-Required-Enterprise-Application-permissions-by-user-request) or [Option 2](#Option-2:-Provide-admin-consent-by-authenticating-to-the-application-as-an-admin) as possible workarounds. + 4. If the administrator receives an error while attempting to provide consent manually, try either [Option 1](#Option-1-Approve-enterprise-application-permissions-by-user-request) or [Option 2](#Option-2-Provide-admin-consent-by-authenticating-the-application-as-an-admin) as possible workarounds.   -## Option 1: Approve Required Enterprise Application permissions by user request +## Option 1 Approve enterprise application permissions by user request > [!Note] > This is currently a preview feature. Azure Active Directory admins will need to allow for users to request admin consent to apps. Verify the setting is configured to **Yes** in [Enterprise applications](https://portal.azure.com/#blade/Microsoft_AAD_IAM/StartboardApplicationsMenuBlade/UserSettings/menuId/). ![Enterprise applications user settings](images/msi-enterprise-app-user-setting.jpg) -More information is available in [Configure Admin consent workflow](https://docs.microsoft.com/en-us/azure/active-directory/manage-apps/configure-admin-consent-workflow). +More information is available in [Configure Admin consent workflow](https://docs.microsoft.com/azure/active-directory/manage-apps/configure-admin-consent-workflow). -Once this setting is verified, users can go through the enterprise customer sign-in at [Microsoft security intelligence](https://www.microsoft.com/en-us/wdsi/filesubmission), and submit a request for admin consent, including justification. +Once this setting is verified, users can go through the enterprise customer sign-in at [Microsoft security intelligence](https://www.microsoft.com/wdsi/filesubmission), and submit a request for admin consent, including justification. ![Contoso sign in flow](images/msi-contoso-approval-required.png) @@ -53,8 +53,8 @@ Admin will be able to review and approve the application permissions [Azure admi After providing consent, all users in the tenant will be able to use the application.   -## Option 2: Provide admin consent by authenticating the application as an admin -This process requires that global admins go through the Enterprise customer sign-in flow at [Microsoft security intelligence](https://www.microsoft.com/en-us/wdsi/filesubmission). +## Option 2 Provide admin consent by authenticating the application as an admin +This process requires that global admins go through the Enterprise customer sign-in flow at [Microsoft security intelligence](https://www.microsoft.com/wdsi/filesubmission). ![Consent sign in flow](images/msi-microsoft-permission-required.jpg) Then, admins review the permissions and make sure to select **Consent on behalf of your organization**, and click **Accept**. @@ -69,7 +69,7 @@ and click **delete**. 2. Capture TenantID from [Properties](https://portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/Properties). 3. Replace {tenant-id} with the specific tenant that needs to grant consent to this application in the URL below. Copy this URL into browser. The rest of the parameters are already completed. -``https://login.microsoftonline.com/{tenant-id}/v2.0/adminconsent?client_id=f0cf43e5-8a9b-451c-b2d5-7285c785684d&state=12345&redirect_uri=https%3a%2f%2fwww.microsoft.com%2fen-us%2fwdsi%2ffilesubmission&scope=openid+profile+email+offline_access`` +``https://login.microsoftonline.com/{tenant-id}/v2.0/adminconsent?client_id=f0cf43e5-8a9b-451c-b2d5-7285c785684d&state=12345&redirect_uri=https%3a%2f%2fwww.microsoft.com%2fwdsi%2ffilesubmission&scope=openid+profile+email+offline_access`` ![Permissions needed](images/msi-microsoft-permission-requested-your-organization.png) @@ -79,6 +79,6 @@ and click **delete**. ![Review that permissions are applied](images/msi-permissions.jpg) -4. Sign in to [Microsoft security intelligence](https://www.microsoft.com/en-us/wdsi/filesubmission) as an enterprise user with a non-admin account to see if you have access. +4. Sign in to [Microsoft security intelligence](https://www.microsoft.com/wdsi/filesubmission) as an enterprise user with a non-admin account to see if you have access. If the warning is not resolved after following these troubleshooting steps, call Microsoft support.