You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/active-directory/develop/howto-app-gallery-listing.md
+26-1Lines changed: 26 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ ms.service: active-directory
10
10
ms.subservice: develop
11
11
ms.topic: conceptual
12
12
ms.workload: identity
13
-
ms.date: 09/16/2019
13
+
ms.date: 12/06/2019
14
14
ms.author: ryanwi
15
15
ms.reviewer: jeedes
16
16
ms.custom: aaddev, seoapril2019
@@ -39,6 +39,10 @@ This article shows how to list an application in the Azure Active Directory (Azu
39
39
- For password SSO, make sure that your application supports form authentication so that password vaulting can be done to get single sign-on to work as expected.
40
40
- You need a permanent account for testing with at least two users registered.
41
41
42
+
**How to get Azure AD for developers?**
43
+
44
+
You can get a free test account with all the premium Azure AD features - 90 days free and can get extended as long as you do dev work with it: https://docs.microsoft.com/office/developer-program/office-365-developer-program
45
+
42
46
## Submit the request in the portal
43
47
44
48
After you've tested that your application integration works with Azure AD, submit your request for access in the [Application Network portal](https://microsoft.sharepoint.com/teams/apponboarding/Apps). If you have an Office 365 account, use that to sign in to this portal. If not, use your Microsoft account, such as Outlook or Hotmail, to sign in.
@@ -57,6 +61,26 @@ Our team reviews the details and gives you access accordingly. After your reques
57
61
58
62

59
63
64
+
## Issues on logging into portal
65
+
66
+
If you are seeing this error while logging in then here are the detail on the issue and this is how you can fix it.
67
+
68
+
* If your sign-in was blocked as shown below:
69
+
70
+

71
+
72
+
**What’s happening:**
73
+
74
+
The guest user is federated to a home tenant which is also an Azure AD. The guest user is at High risk. Microsoft doesn’t allow High risk users to access its resources. All High risk users (employees or guests / vendors) must remediate / close their risk to access Microsoft resources. For guest users, this user risk comes from the home tenant and the policy comes from the resource tenant (Microsoft in this case).
75
+
76
+
**Secure solutions:**
77
+
78
+
* MFA registered guest users remediate their own user risk. This can be done by the guest user performing a secured password change or reset (https://aka.ms/sspr) at their home tenant (this needs MFA and SSPR at the home tenant). The secured password change or reset must be initiated on Azure AD and not on-prem.
79
+
80
+
* Guest users have their admins remediate their risk. In this case, the admin will perform a password reset (temporary password generation). This does not need Identity Protection. The guest user’s admin can go to https://aka.ms/RiskyUsers and click on ‘Reset password’.
81
+
82
+
* Guest users have their admins close / dismiss their risk. Again, this does not need Identity Protection. The admin can go to https://aka.ms/RiskyUsers and click on ‘Dismiss user risk’. However, the admin must do the due diligence to ensure this was a false positive risk assessment before closing the user risk. Otherwise, they are putting their and Microsoft’s resources at risk by suppressing a risk assessment without investigation.
83
+
60
84
> [!NOTE]
61
85
> If you have any issues with access, contact the [Azure AD SSO Integration Team](<mailto:[email protected]>).
62
86
@@ -76,6 +100,7 @@ To list an application in the Azure AD app gallery, you first need to implement
76
100

77
101
78
102
* If you want to add your application to list in the gallery by using **SAML 2.0** or **WS-Fed**, select **SAML 2.0/WS-Fed** as shown.
103
+
79
104
* If you have any issues with access, contact the [Azure AD SSO Integration Team](<mailto:[email protected]>).
0 commit comments