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
For information about connectors, see [Understand Azure AD Application Proxy connectors](application-proxy-understand-connectors.md).
78
+
77
79
For high availability purposes, you should deploy at least two connectors. To deploy more connectors, repeat steps 2 and 3, above. Each connector must be registered separately.
78
80
79
81
If you want to uninstall the Connector, uninstall both the Connector service and the Updater service. Restart your computer to fully remove the service.
Copy file name to clipboardExpand all lines: articles/active-directory/active-directory-application-proxy-get-started.md
+5-2Lines changed: 5 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -50,9 +50,11 @@ With Azure AD Application Proxy you can access different types of internal appli
50
50
* Web APIs that you want to expose to rich applications on different devices
51
51
* Applications hosted behind a Remote Desktop Gateway
52
52
53
-
## How does it work?
53
+
## How does the service work with connectors?
54
54
Application Proxy works by installing a slim Windows Server service called a connector inside your network. With the connector, you don't have to open any inbound ports or put anything in the DMZ. If you have high traffic in your apps you can add more connectors, and the service takes care of the load balancing. The connectors are stateless and pull everything from the cloud as necessary.
55
55
56
+
For information about connectors, see [Understand Azure AD Application Proxy connectors](application-proxy-understand-connectors.md).
57
+
56
58
When users access applications remotely, they connect to the published endpoint. Users authenticate in Azure AD and then are routed through the connector to the on-premises application.
@@ -73,13 +75,14 @@ Make sure you have an Azure AD basic or premium subscription and an Azure AD dir
73
75
74
76
Setting up Application Proxy is accomplished in two steps:
75
77
76
-
1.[Enable Application Proxy and configure the connector](active-directory-application-proxy-enable.md)
78
+
1.[Enable Application Proxy and configure the connector](active-directory-application-proxy-enable.md).
77
79
2.[Publish applications](active-directory-application-proxy-publish.md) - use the quick and easy wizard to get your on-premises apps published and accessible remotely.
78
80
79
81
## What's next?
80
82
There's a lot more you can do with Application Proxy:
81
83
82
84
*[Publish applications using your own domain name](active-directory-application-proxy-custom-domains.md)
85
+
*[Working with existing on-premise Proxy servers](application-proxy-working-with-proxy-servers.md)
Copy file name to clipboardExpand all lines: articles/active-directory/active-directory-integrating-applications-getting-started.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: Integrating Azure Active Directory with applications getting started guide | Microsoft Docs
2
+
title: Get started integrating Azure AD with apps | Microsoft Docs
3
3
description: This article is a getting started guide for integrating Azure Active Directory (AD) with on-premises applications, and cloud applications.
Copy file name to clipboardExpand all lines: articles/active-directory/active-directory-reporting-retention.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,8 +27,8 @@ How can you get the collection of activity data started?
27
27
28
28
| Azure AD Edition | Collection Start |
29
29
| :-- | :-- |
30
-
|Premium and Premium 2| When you sign-up for a license|
31
-
| Free | The first time you open the [Azure Active Directory blade](https://ms.portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/Overview) or use the [reporting APIs](https://aka.ms/aadreports)|
30
+
| Azure AD Premium P1 <br /> Azure AD Premium P2| When you sign-up for a subscription|
31
+
|Azure AD Free | The first time you open the [Azure Active Directory blade](https://ms.portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/Overview) or use the [reporting APIs](https://aka.ms/aadreports)|
32
32
33
33
34
34
When is your activity data available in the Azure portal?
@@ -43,14 +43,14 @@ For how long is the collected data stored?
43
43
44
44
**Activity reports**
45
45
46
-
| Report | Azure AD Free | Azure AD Premium 1| Azure AD Premium 2|
46
+
| Report | Azure AD Free | Azure AD Premium P1| Azure AD Premium P2|
47
47
| :-- | :-- | :-- | :-- |
48
48
| Directory Audit | 7 days | 30 days | 30 days |
49
49
| Sign-in Activity | 7 days | 30 days | 30 days |
50
50
51
51
**Security Signals**
52
52
53
-
| Report | Azure AD Free | Azure AD Premium 1| Azure AD Premium 2|
53
+
| Report | Azure AD Free | Azure AD Premium P1| Azure AD Premium P2|
||[Brightspace by Desire2Learn](https://go.microsoft.com/fwLink/?LinkID=522561&clcid=0x409)|
@@ -103,6 +106,7 @@ For the comprehensive list of SaaS apps that have been pre-integrated into Azure
103
106
||[Dow Jones Factiva](https://go.microsoft.com/fwLink/?LinkID=828376&clcid=0x409)|
104
107
||[Dropbox for Business](https://go.microsoft.com/fwLink/?LinkID=309581&clcid=0x409)|
@@ -244,13 +248,13 @@ For the comprehensive list of SaaS apps that have been pre-integrated into Azure
244
248
||[SilkRoad Life Suite](https://go.microsoft.com/fwLink/?LinkID=530238&clcid=0x409)|
||[Splunk Enterprise and Splunk Cloud](https://go.microsoft.com/fwLink/?LinkID=808003&clcid=0x409)|
||[Workplace by Facebook](http://go.microsoft.com/fwlink/?LinkID=708665&clcid=0x409)|
Copy file name to clipboardExpand all lines: articles/active-directory/develop/active-directory-devhowto-multi-tenant-overview.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: How to build an application that can sign in any Azure Active Directory user| Microsoft Docs
2
+
title: How to build an app that can sign in any Azure AD user| Microsoft Docs
3
3
description: Step by step instructions for building an application that can sign in a user from any Azure Active Directory tenant, also known as a multi-tenant application.
4
4
services: active-directory
5
5
documentationcenter: ''
@@ -13,7 +13,7 @@ ms.devlang: na
13
13
ms.topic: article
14
14
ms.tgt_pltfrm: na
15
15
ms.workload: identity
16
-
ms.date: 01/07/2017
16
+
ms.date: 01/23/2017
17
17
ms.author: skwan;bryanla
18
18
19
19
---
@@ -38,7 +38,7 @@ Let’s look at each step in detail. You can also jump straight to [this list of
38
38
## Update registration to be multi-tenant
39
39
By default, web app/API registrations in Azure AD are single tenant. You can make your registration multi-tenant by finding the “Application is Multi-Tenant” switch on the configuration page of your application registration in the [Azure classic portal][AZURE-classic-portal] and setting it to “Yes”.
40
40
41
-
Note: Before an application can be made multi-tenant, Azure AD requires the App ID URI of the application to be globally unique. The App ID URI is one of the ways an application is identified in protocol messages. For a single tenant app, it is sufficient for the App ID URI to be unique within that tenant. For a multi-tenant application, it must be globally unique so Azure AD can find the application across all tenants. Global uniqueness is enforced by requiring the App ID URI to have a host name that matches a verified domain of the Azure AD tenant. For example, if the name of your tenant was contoso.onmicrosoft.com then a valid App ID URI would be `https://contoso.onmicrosoft.com/myapp`. If your tenant had a verified domain of `contoso.com`, then a valid App ID URI would also be `https://contoso.com/myapp`. Setting an application as multi-tenant will fail if the App ID URI doesn’t follow this pattern.
41
+
Also note, before an application can be made multi-tenant, Azure AD requires the App ID URI of the application to be globally unique. The App ID URI is one of the ways an application is identified in protocol messages. For a single tenant app, it is sufficient for the App ID URI to be unique within that tenant. For a multi-tenant application, it must be globally unique so Azure AD can find the application across all tenants. Global uniqueness is enforced by requiring the App ID URI to have a host name that matches a verified domain of the Azure AD tenant. For example, if the name of your tenant was contoso.onmicrosoft.com then a valid App ID URI would be `https://contoso.onmicrosoft.com/myapp`. If your tenant had a verified domain of `contoso.com`, then a valid App ID URI would also be `https://contoso.com/myapp`. Setting an application as multi-tenant will fail if the App ID URI doesn’t follow this pattern.
42
42
43
43
Native client registrations are multi-tenant by default. You don’t need to take any action to make a native client application registration multi-tenant.
0 commit comments