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/authentication/howto-password-ban-bad-configure.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@ Many organizations find their users create passwords using common local words su
21
21
22
22
## Add to the custom list
23
23
24
-
Configuring the custom banned password list requires an Azure Active Directory Premium P1 or P2 license. For more detailed information about Azure Active Directory licensing, see the [Azure Active Directory pricing page](https://azure.microsoft.com/pricing/details/active-directory/).|
24
+
Configuring the custom banned password list requires an Azure Active Directory Premium P1 or P2 license. For more detailed information about Azure Active Directory licensing, see the [Azure Active Directory pricing page](https://azure.microsoft.com/pricing/details/active-directory/).
25
25
26
26
1. Sign in to the [Azure portal](https://portal.azure.com) and browse to **Azure Active Directory**, **Authentication methods**, then **Password protection**.
27
27
1. Set the option **Enforce custom list**, to **Yes**.
Copy file name to clipboardExpand all lines: articles/active-directory/develop/about-microsoft-identity-platform.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -55,7 +55,7 @@ The **application API in Microsoft Graph** is currently in preview. Use this API
55
55
56
56
### MSAL libraries
57
57
58
-
You can use the MSAL library to build applications that authenticate all Microsoft identities. The MSAL libraries in .NET are generally available. MSAL libraries for JavaScript, iOS, and Android are in preview and suitable for use in a production environment. We provide the same production level support for MSAL libraries in preview as we do for versions of MSAL and ADAL that are generally available.
58
+
You can use the MSAL library to build applications that authenticate all Microsoft identities. The MSAL libraries in .NET and JavaScript are generally available. MSAL libraries for iOS and Android are in preview and suitable for use in a production environment. We provide the same production level support for MSAL libraries in preview as we do for versions of MSAL and ADAL that are generally available.
59
59
60
60
You can also use the MSAL libraries to integrate your application with Azure AD B2C.
Copy file name to clipboardExpand all lines: articles/active-directory/hybrid/cloud-governed-management-for-on-premises.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -89,7 +89,7 @@ For an organization that already uses an on-premises identity provider, moving a
89
89
90
90

91
91
92
-
To begin migrating federated applications to Azure AD as the identity provider, refer to, that, includes links to:
92
+
To begin migrating federated applications to Azure AD as the identity provider, refer tohttps://aka.ms/migrateapps that includes links to:
93
93
94
94
* The white paper [Migrating Your Applications to Azure Active Directory](https://aka.ms/migrateapps/whitepaper), which presents the benefits of migration and describes how to plan for migration in four clearly-outlined phases: discovery, classification, migration, and ongoing management. You'll be guided through how to think about the process and break down your project into easy-to-consume pieces. Throughout the document are links to important resources that will help you along the way.
Copy file name to clipboardExpand all lines: articles/active-directory/manage-apps/application-sign-in-problem-application-error.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -68,7 +68,7 @@ Next time the user signs in to the application, Azure AD send the new attribute
68
68
69
69
The sign-in to the application is failing because the SAML response is missing attributes such as roles or because the application is expecting a different format or value for the EntityID attribute.
70
70
71
-
If you're using [Azure AD automated user provisioning](https://docs.microsoft.com/en-us/azure/active-directory/manage-apps/user-provisioning) to create, maintain, and remove users in the application. Then, verify that the user has been successfully provisioned to the SaaS application. For more information, see [No users are being provisioned to an Azure AD Gallery application](https://docs.microsoft.com/en-us/azure/active-directory/manage-apps/application-provisioning-config-problem-no-users-provisioned)
71
+
If you're using [Azure AD automated user provisioning](https://docs.microsoft.com/azure/active-directory/manage-apps/user-provisioning) to create, maintain, and remove users in the application. Then, verify that the user has been successfully provisioned to the SaaS application. For more information, see [No users are being provisioned to an Azure AD Gallery application](https://docs.microsoft.com/azure/active-directory/manage-apps/application-provisioning-config-problem-no-users-provisioned)
72
72
73
73
## Add an attribute in the Azure AD application configuration:
Copy file name to clipboardExpand all lines: articles/active-directory/manage-apps/use-scim-to-provision-users-and-groups.md
+2-3Lines changed: 2 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -78,7 +78,7 @@ Applications that support the SCIM profile described in this article can be conn
78
78
*Figure 3: Configuring provisioning in the Azure portal*
79
79
80
80
1. In the **Tenant URL** field, enter the URL of the application's SCIM endpoint. Example: https://api.contoso.com/scim/v2/
81
-
1. If the SCIM endpoint requires an OAuth bearer token from an issuer other than Azure AD, then copy the required OAuth bearer token into the optional **Secret Token** field. If this field is left blank, Azure AD includes an OAuth bearer token issued from Azure AD with each request. Apps that use Azure AD as an identity provider can validate this Azure AD-issued token.
81
+
1. If the SCIM endpoint requires an OAuth bearer token from an issuer other than Azure AD, then copy the required OAuth bearer token into the optional **Secret Token** field.
82
82
1. Select **Test Connection** to have Azure Active Directory attempt to connect to the SCIM endpoint. If the attempt fails, error information is displayed.
83
83
84
84
>[!NOTE]
@@ -664,8 +664,7 @@ The easiest way to implement a SCIM endpoint that can accept provisioning reques
664
664
665
665
1. In the **Tenant URL** field, enter the internet-exposed URL and port of your SCIM endpoint. The entry is something like http://testmachine.contoso.com:9000 or http://\<ip-address>:9000/, where \<ip-address> is the internet exposed IP address.
666
666
667
-
1. If the SCIM endpoint requires an OAuth bearer token from an issuer other than Azure AD, then copy the required OAuth bearer token into the optional **Secret Token** field. If this field is left blank, Azure AD will include an OAuth bearer token issued from Azure AD with each request. Apps that use Azure AD as an identity provider can validate this Azure AD -issued token.
668
-
667
+
1. If the SCIM endpoint requires an OAuth bearer token from an issuer other than Azure AD, then copy the required OAuth bearer token into the optional **Secret Token** field.
669
668
1. Select **Test Connection** to have Azure Active Directory attempt to connect to the SCIM endpoint. If the attempt fails, error information is displayed.
*[Arguments](../container-instances/container-instances-exec.md#restrictions) for exec in ACI
66
66
*[Daemonsets](concepts-clusters-workloads.md#statefulsets-and-daemonsets) will not deploy pods to the virtual node
67
+
*[Windows Server nodes (currently in preview in AKS)](windows-container-cli.md) are not supported alongside virtual nodes. You can use virtual nodes to schedule Windows Server containers without the need for Windows Server nodes in an AKS cluster.
*[Arguments](../container-instances/container-instances-exec.md#restrictions) for exec in ACI
66
66
*[Daemonsets](concepts-clusters-workloads.md#statefulsets-and-daemonsets) will not deploy pods to the virtual node
67
+
*[Windows Server nodes (currently in preview in AKS)](windows-container-cli.md) are not supported alongside virtual nodes. You can use virtual nodes to schedule Windows Server containers without the need for Windows Server nodes in an AKS cluster.
Copy file name to clipboardExpand all lines: articles/cloud-services/cloud-services-guestos-msrc-releases.md
+52-54Lines changed: 52 additions & 54 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ ms.devlang: na
12
12
ms.topic: article
13
13
ms.tgt_pltfrm: na
14
14
ms.workload: tbd
15
-
ms.date: 5/23/2019
15
+
ms.date: 6/6/2019
16
16
ms.author: raiye
17
17
18
18
---
@@ -21,51 +21,49 @@ The following tables show the Microsoft Security Response Center (MSRC) updates
21
21
22
22
## May 2019 Guest OS
23
23
24
-
>[!NOTE]
25
-
>The May Guest OS is currently being rolled out to Cloud Service VMs that are configured for automatic updates. When the rollout is complete, this version will be made available for manual updates through the Azure portal and configuration files. The following patches are included in the May Guest OS. This list is subject to change.
26
-
27
24
| Product Category | Parent KB Article | Vulnerability Description | Guest OS | Date First Introduced |
28
25
| --- | --- | --- | --- | --- |
29
-
| Rel 19-05 |[4498206 ]| May IE Rollup | 2,86, 3.73, 4.66 | May 14, 2019 |
30
-
| Rel 19-05 |[4505050 ]| May IE Rollup | 2,86, 3.73, 4.66 | May 18, 2019 |
31
-
| Rel 19-05 |[4497932 ]| May Flash Update | 3.73, 4.66, 5.31 | May 14, 2019 |
32
-
| Rel 19-05 |[4499175 ]| May Security Rollup | 2.86 | May 14, 2019 |
33
-
| Rel 19-05 |[4495612 ]| May Security Rollup .NET 3.5 | 2.86 | May 14, 2019 |
34
-
| Rel 19-05 |[4495593 ]| May Security Rollup .NET 4.5.2 | 2.86 | May 14, 2019 |
35
-
| Rel 19-05 |[4499158 ]| May Security Rollup | 3.73 | May 14, 2019 |
36
-
| Rel 19-05 |[4495607 ]| May Security Rollup .NET 3.5 | 3.73 | May 14, 2019 |
37
-
| Rel 19-05 |[4495591 ]| May Security Rollup .NET 4.5.2 | 3.73 | May 14, 2019 |
0 commit comments