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
Over the years the directory integration tools have grown and evolved. This document is to help provide a consolidated view of these tools and a comparison of the features that are available in each.
22
-
23
-
<!-- The hardcoded link is a workaround for campaign ids not working in acom links-->
24
-
25
-
> [!NOTE]
26
-
> Azure AD Connect incorporates the components and functionality previously released as Dirsync and AAD Sync. These tools are no longer being released individually, and all future improvements will be included in updates to Azure AD Connect, so that you always know where to get the most current functionality.
27
-
>
28
-
> DirSync and Azure AD Sync are deprecated. More information can be found in [here](reference-connect-dirsync-deprecated.md).
29
-
>
30
-
>
31
-
32
-
Use the following key for each of the tables.
33
-
34
-
● = Available Now
35
-
FR = Future Release
36
-
PP = Public Preview
37
-
38
-
## On-Premises to Cloud Synchronization
39
-
| Feature | Azure Active Directory Connect | Azure Active Directory Synchronization Services (AAD Sync) - NO LONGER SUPPORTED | Azure Active Directory Synchronization Tool (DirSync) - NO LONGER SUPPORTED | Forefront Identity Manager 2010 R2 (FIM) | Microsoft Identity Manager 2016 (MIM) |
40
-
|:--- |:---:|:---:|:---:|:---:|:---:|
41
-
| Connect to single on-premises AD forest |● |● |● |● |● |
42
-
| Connect to multiple on-premises AD forests |● |● ||● |● |
43
-
| Connect to multiple on-premises Exchange Orgs |● |||||
44
-
| Connect to single on-premises LDAP directory |●*|||● |● |
45
-
| Connect to multiple on-premises LDAP directories |●*|||● |● |
46
-
| Connect to on-premises AD and on-premises LDAP directories |●*|||● |● |
47
-
| Connect to custom systems (i.e. SQL, Oracle, MySQL, etc.) |FR |||● |● |
48
-
| Synchronize customer defined attributes (directory extensions) |● |||||
| Supports FIM synchronization rules and connectors for provisioning to on-premises systems. ||||● |● |
51
-
52
-
53
-
* Currently there are two supported options for this. They are:
54
-
55
-
1. You can use the generic LDAP connector and enable it outside of Azure AD Connect. This is complex and requires a partner for on-boarding and a premier support agreement to maintain. This option can handle both single and multiple LDAP directories.
56
-
57
-
2. You can develop your own solution for moving objects from LDAP to Active Directory. Then synchronize the objects with Azure AD Connect. MIM or FIM could be used as a possible solution for moving the objects.
58
-
59
-
## Cloud to On-Premises Synchronization
60
-
| Feature | Azure Active Directory Connect | Azure Active Directory Synchronization Services- NO LONGER SUPPORTED | Azure Active Directory Synchronization Tool (DirSync)- NO LONGER SUPPORTED | Forefront Identity Manager 2010 R2 (FIM) | Microsoft Identity Manager 2016 (MIM) |
| Writeback of passwords (from self-service password reset (SSPR) and password change) |● |● ||||
20
+
Over the years the directory integration tools have grown and evolved.
66
21
67
-
## Authentication Feature Support
68
-
| Feature | Azure Active Directory Connect | Azure Active Directory Synchronization Services- NO LONGER SUPPORTED | Azure Active Directory Synchronization Tool (DirSync)- NO LONGER SUPPORTED | Forefront Identity Manager 2010 R2 (FIM) | Microsoft Identity Manager 2016 (MIM) |
69
-
|:--- |:---:|:---:|:---:|:---:|:---:|
70
-
| Password Hash Sync for single on-premises AD forest |●|●|● |||
71
-
| Password Hash Sync for multiple on-premises AD forests |●|● ||||
72
-
| Pass-Through Authentication for single on-premises AD forests |●|||||
73
-
| Single Sign-on with Federation |● |● |● |● |● |
74
-
| Seamless Single Sign-on|● |||||
75
-
| Writeback of passwords (from SSPR and password change) |● |● ||||
76
22
77
-
## Set-up and Installation
78
-
| Feature | Azure Active Directory Connect | Azure Active Directory Synchronization Services- NO LONGER SUPPORTED | Azure Active Directory Synchronization Tool (DirSync)- NO LONGER SUPPORTED | Microsoft Identity Manager 2016 (MIM) |
79
-
|:--- |:---:|:---:|:---:|:---:|
80
-
| Supports installation on a Domain Controller |● |● |● ||
81
-
| Supports installation using SQL Express |● |● |● ||
82
-
| Easy upgrade from DirSync |● ||||
83
-
| Localization of Admin UX to Windows Server languages |● |● |● ||
84
-
| Localization of end user UX to Windows Server languages ||||● |
85
-
| Support for Windows Server 2008 and Windows Server 2008 R2 |● for Sync, No for federation |● |● |● |
86
-
| Support for Windows Server 2012 and Windows Server 2012 R2 |● |● |● |● |
23
+
-[FIM](https://docs.microsoft.com/previous-versions/windows/desktop/forefront-2010/ff182370%28v%3dvs.100%29) and [MIM](https://docs.microsoft.com/microsoft-identity-manager/microsoft-identity-manager-2016) are still supported and primarily enable synchronization between on-premises systems. The [FIM Windows Azure AD Connector](https://docs.microsoft.com/previous-versions/mim/dn511001(v=ws.10)?redirectedfrom=MSDN) is supported in both FIM and MIM, but not recommended for new deployments - customers with on-premises sources such as Notes or SAP HCM should use MIM to populate Active Directory Domain Services (AD DS) and then also use either Azure AD Connect sync or Azure AD Connect cloud provisioning to synchronize from AD DS to Azure AD.
24
+
-[Azure AD Connect sync](how-to-connect-sync-whatis.md) incorporates the components and functionality previously released in DirSync and Azure AD Sync, for synchronizing between AD DS forests and Azure AD.
25
+
-[Azure AD Connect cloud provisioning](../cloud-provisioning/what-is-cloud-provisioning.md) is a new Microsoft agent for synching from AD DS to Azure AD, useful for scenarios such as merger and acquisition where the acquired company's AD forests are isolated from the parent company's AD forests.
87
26
88
-
## Filtering and Configuration
89
-
| Feature | Azure Active Directory Connect | Azure Active Directory Synchronization Services- NO LONGER SUPPORTED | Azure Active Directory Synchronization Tool (DirSync)- NO LONGER SUPPORTED | Forefront Identity Manager 2010 R2 (FIM) | Microsoft Identity Manager 2016 (MIM) |
90
-
|:--- |:---:|:---:|:---:|:---:|:---:|
91
-
| Filter on Domains and Organizational Units |● |● |● |● |● |
To learn more about the differences between Azure AD Connect sync and Azure AD Connect cloud provisioning, see the article [What is Azure AD Connect cloud provisioning?](../cloud-provisioning/what-is-cloud-provisioning.md)
97
28
98
29
## Next steps
99
30
Learn more about [Integrating your on-premises identities with Azure Active Directory](whatis-hybrid-identity.md).
thrownewException($"Certificate with thumbprint {certThumbprint} was not found");
77
+
78
+
// Use certificate
79
+
Console.WriteLine(cert.FriendlyName);
80
+
81
+
// Consider to call Dispose() on the certificate after it's being used, avaliable in .NET 4.6 and later
73
82
}
74
-
certStore.Close();
75
-
...
76
83
```
77
84
78
85
In Java code, you access the certificate from the "Windows-MY" store using the Subject Common Name field (see [Public key certificate](https://en.wikipedia.org/wiki/Public_key_certificate)). The following code shows how to load a private key certificate:
@@ -107,10 +114,11 @@ The certificate file names are the certificate thumbprints. The following C# cod
Copy file name to clipboardExpand all lines: articles/application-gateway/features.md
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ services: application-gateway
5
5
author: vhorne
6
6
ms.service: application-gateway
7
7
ms.topic: conceptual
8
-
ms.date: 03/04/2020
8
+
ms.date: 04/07/2020
9
9
ms.author: victorh
10
10
---
11
11
@@ -157,6 +157,10 @@ The following table shows an average performance throughput for each application
157
157
> [!NOTE]
158
158
> These values are approximate values for an application gateway throughput. The actual throughput depends on various environment details, such as average page size, location of back-end instances, and processing time to serve a page. For exact performance numbers, you should run your own tests. These values are only provided for capacity planning guidance.
159
159
160
+
## Version feature comparison
161
+
162
+
For an Application Gateway v1-v2 feature comparison, see [Autoscaling and Zone-redundant Application Gateway v2](application-gateway-autoscaling-zone-redundant.md#feature-comparison-between-v1-sku-and-v2-sku)
163
+
160
164
## Next steps
161
165
162
166
- Learn how Application Gateway works - [How an application gateway works](how-application-gateway-works.md)
Copy file name to clipboardExpand all lines: articles/cost-management-billing/costs/assign-access-acm-data.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
@@ -3,7 +3,7 @@ title: Assign access to Azure Cost Management data
3
3
description: This article walks you though assigning permission to Azure Cost Management data for various access scopes.
4
4
author: bandersmsft
5
5
ms.author: banders
6
-
ms.date: 03/19/2020
6
+
ms.date: 04/07/2020
7
7
ms.topic: conceptual
8
8
ms.service: cost-management-billing
9
9
ms.reviewer: adwise
@@ -16,9 +16,9 @@ For users with Azure Enterprise agreements, a combination of permissions granted
16
16
17
17
The scope that a user selects is used throughout Cost Management to provide data consolidation and to control access to cost information. When using scopes, users don't multi-select them. Instead, they select a larger scope that child scopes roll up to and then they filter-down to what they want to view. Data consolidation is important to understand because some people shouldn't access a parent scope that child scopes roll up to.
18
18
19
-
Watch the [How to assign access with Azure Cost Management](https://www.youtube.com/watch?v=J997ckmwTa8) video to learn about assigning access to view costs and charges with Azure role-based access control.
19
+
Watch the [Cost Management controlling access](https://www.youtube.com/watch?v=_uQzQ9puPyM) video to learn about assigning access to view costs and charges with Azure role-based access control.
description: This quickstart helps you use cost analysis to explore and analyze your Azure organizational costs.
4
4
author: bandersmsft
5
5
ms.author: banders
6
-
ms.date: 03/24/2020
6
+
ms.date: 04/07/2020
7
7
ms.topic: quickstart
8
8
ms.service: cost-management-billing
9
9
ms.reviewer: micflan
@@ -139,6 +139,10 @@ You can view the full dataset for any view. Whichever selections or filters that
139
139
140
140
## Understanding grouping and filtering options
141
141
142
+
Cost analysis has many grouping and filtering options. To watch a video about grouping and filtering options, watch the [Cost Management reporting by dimensions and tags](https://www.youtube.com/watch?v=2Vx7V17zbmk) video.
Copy file name to clipboardExpand all lines: articles/cost-management-billing/costs/understand-work-scopes.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,6 +22,10 @@ A _scope_ is a node in the Azure resource hierarchy where Azure AD users access
22
22
23
23
Scopes are where you manage billing data, have roles specific to payments, view invoices, and conduct general account management. Billing and account roles are managed separately from those used for resource management, which use [Azure RBAC](../../role-based-access-control/overview.md). To clearly distinguish the intent of the separate scopes, including the access control differences, these are referred to as _billing scopes_ and _RBAC scopes_, respectively.
24
24
25
+
To learn more about scopes, watch the [Cost Management setting up hierarchies](https://www.youtube.com/watch?v=n3TLRaYJ1NY) video.
Cost Management works at all scopes above resources to allow organizations to manage costs at the level at which they have access, whether that's the entire billing account or a single resource group. Although billing scopes differ based on your Microsoft agreement (subscription type), the RBAC scopes do not.
The simplest way to authenticate a cloud-based .NET application is with a managed identity; see [Use an App Service managed identity to access Azure Key Vault](managed-identity.md) for details. For the sake of simplicity however, this quickstart creates a .NET console application. Authenticating a desktop application with Azure requires the use of a service principal and an access control policy.
66
+
The simplest way to authenticate a cloud-based Python application is with a managed identity; see [Use an App Service managed identity to access Azure Key Vault](managed-identity.md) for details. For the sake of simplicity however, this quickstart creates a Python console application. Authenticating a desktop application with Azure requires the use of a service principal and an access control policy.
67
67
68
68
Create a service principle using the Azure CLI [az ad sp create-for-rbac](/cli/azure/ad/sp?view=azure-cli-latest#az-ad-sp-create-for-rbac) command:
0 commit comments