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
| Angular |[MSAL Angular v2](https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/dev/lib/msal-angular)<sup>2</sup> |[msal-angular](https://www.npmjs.com/package/@azure/msal-angular)|[Tutorial](../../tutorial-v2-angular-auth-code.md)|![Library can request ID tokens for user sign-in.][y]|![Library can request access tokens for protected web APIs.][y]| GA |
12
12
| Angular |[MSAL Angular](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/msal-angular-v1/lib/msal-angular)<sup>3</sup> |[msal-angular](https://www.npmjs.com/package/@azure/msal-angular)| — |![Library can request ID tokens for user sign-in.][y]|![Library can request access tokens for protected web APIs.][y]| GA |
13
-
| AngularJS |[MSAL AngularJS](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/dev/maintenance/msal-angularjs)<sup>3</sup> |[msal-angularjs](https://www.npmjs.com/package/@azure/msal-angular)| — |![Library can request ID tokens for user sign-in.][y]|![Library can request access tokens for protected web APIs.][y]| Public preview |
13
+
| AngularJS |[MSAL AngularJS](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/dev/lib/msal-angular)<sup>3</sup> |[msal-angularjs](https://www.npmjs.com/package/@azure/msal-angular)| — |![Library can request ID tokens for user sign-in.][y]|![Library can request access tokens for protected web APIs.][y]| Public preview |
14
14
| JavaScript |[MSAL.js v2](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/dev/lib/msal-browser)<sup>2</sup> |[msal-browser](https://www.npmjs.com/package/@azure/msal-browser)|[Tutorial](../../tutorial-v2-javascript-auth-code.md)|![Library can request ID tokens for user sign-in.][y]|![Library can request access tokens for protected web APIs.][y]| GA |
15
15
| JavaScript |[MSAL.js 1.0](/javascript/api/overview/msal-overview)<sup>3</sup> |[msal-core](https://www.npmjs.com/package/@azure/msal-core)| — |![Library can request ID tokens for user sign-in.][y]|![Library can request access tokens for protected web APIs.][y]| GA |
16
16
| React |[MSAL React](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/dev/lib/msal-react)<sup>2</sup> |[msal-react](https://www.npmjs.com/package/@azure/msal-react)|[Tutorial](../../single-page-app-tutorial-01-register-app.md)|![Library can request ID tokens for user sign-in.][y]|![Library can request access tokens for protected web APIs.][y]| GA |
Copy file name to clipboardExpand all lines: articles/active-directory/saas-apps/cleanmail-swiss-provisioning-tutorial.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ ms.author: thwimmer
16
16
17
17
# Tutorial: Configure Cleanmail Swiss for automatic user provisioning
18
18
19
-
This tutorial describes the steps you need to do in both Cleanmail Swiss and Azure Active Directory (Azure AD) to configure automatic user provisioning. When configured, Azure AD automatically provisions and deprovisions users and groups to [Cleanmail](https://www.alinto.com/fr) using the Azure AD Provisioning service. For important details on what this service does, how it works, and frequently asked questions, see [Automate user provisioning and deprovisioning to SaaS applications with Azure Active Directory](../app-provisioning/user-provisioning.md).
19
+
This tutorial describes the steps you need to do in both Cleanmail Swiss and Azure Active Directory (Azure AD) to configure automatic user provisioning. When configured, Azure AD automatically provisions and deprovisions users to [Cleanmail](https://www.alinto.com/fr) using the Azure AD Provisioning service. For important details on what this service does, how it works, and frequently asked questions, see [Automate user provisioning and deprovisioning to SaaS applications with Azure Active Directory](../app-provisioning/user-provisioning.md).
20
20
21
21
22
22
## Capabilities supported
@@ -36,7 +36,7 @@ The scenario outlined in this tutorial assumes that you already have the followi
36
36
37
37
## Step 1. Plan your provisioning deployment
38
38
1. Learn about [how the provisioning service works](../app-provisioning/user-provisioning.md).
39
-
1. Determine who will be in [scope for provisioning](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md).
39
+
1. Determine who is in [scope for provisioning](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md).
40
40
1. Determine what data to [map between Azure AD and Cleanmail](../app-provisioning/customize-application-attributes.md).
41
41
42
42
## Step 2. Configure Cleanmail Swiss to support provisioning with Azure AD
Add Cleanmail Swiss from the Azure AD application gallery to start managing provisioning to Cleanmail. If you have previously setup Cleanmail Swiss for SSO, you can use the same application. However it's recommended you create a separate app when testing out the integration initially. Learn more about adding an application from the gallery [here](../manage-apps/add-application-portal.md).
49
49
50
-
## Step 4. Define who will be in scope for provisioning
50
+
## Step 4. Define who is in scope for provisioning
51
51
52
-
The Azure AD provisioning service allows you to scope who will be provisioned based on assignment to the application and or based on attributes of the user and group. If you choose to scope who will be provisioned to your app based on assignment, you can use the following [steps](../manage-apps/assign-user-or-group-access-portal.md) to assign users and groups to the application. If you choose to scope who will be provisioned based solely on attributes of the user or group, you can use a scoping filter as described [here](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md).
52
+
The Azure AD provisioning service allows you to scope who is provisioned based on assignment to the application and or based on attributes of the user. If you choose to scope who is provisioned to your app based on assignment, you can use the following [steps](../manage-apps/assign-user-or-group-access-portal.md) to assign users to the application. If you choose to scope who is provisioned based solely on attributes of the user, you can use a scoping filter as described [here](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md).
53
53
54
-
* Start small. Test with a small set of users and groups before rolling out to everyone. When scope for provisioning is set to assigned users and groups, you can control this by assigning one or two users or groups to the app. When scope is set to all users and groups, you can specify an [attribute based scoping filter](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md).
54
+
* Start small. Test with a small set of users before rolling out to everyone. When the scope for provisioning is set to assigned users, you can control this by assigning one or two users to the app instance. When scope is set to all users, you can specify an [attribute based scoping filter](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md).
55
55
56
56
* If you need more roles, you can [update the application manifest](../develop/howto-add-app-roles-in-azure-ad-apps.md) to add new roles.
57
57
58
58
59
59
## Step 5. Configure automatic user provisioning to Cleanmail Swiss
60
60
61
-
This section guides you through the steps to configure the Azure AD provisioning service to create, update, and disable users and groups in Cleanmail Swiss based on user and group assignments in Azure AD.
61
+
This section guides you through the steps to configure the Azure AD provisioning service to create, update, and disable users in Cleanmail Swiss based on user assignments in Azure AD.
62
62
63
63
### To configure automatic user provisioning for Cleanmail Swiss in Azure AD:
64
64
@@ -106,15 +106,15 @@ This section guides you through the steps to configure the Azure AD provisioning
106
106
107
107
108
108
109
-
1. Define the users and groups that you would like to provision to Cleanmail Swiss by choosing the desired values in **Scope** in the **Settings** section.
109
+
1. Define the users that you would like to provision to Cleanmail Swiss by choosing the desired values in **Scope** in the **Settings** section.
110
110
111
111
112
112
113
113
1. When you're ready to provision, click **Save**.
114
114
115
115
116
116
117
-
This operation starts the initial synchronization cycle of all users and groups defined in **Scope** in the **Settings** section. The initial cycle takes longer to complete than next cycles, which occur approximately every 40 minutes as long as the Azure AD provisioning service is running.
117
+
This operation starts the initial synchronization cycle of all users defined in **Scope** in the **Settings** section. The initial cycle takes longer to complete than next cycles, which occur approximately every 40 minutes as long as the Azure AD provisioning service is running.
118
118
119
119
## Step 6. Monitor your deployment
120
120
Once you've configured provisioning, use the following resources to monitor your deployment:
Copy file name to clipboardExpand all lines: articles/aks/load-balancer-standard.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
@@ -319,7 +319,7 @@ az aks create \
319
319
By default, AKS sets *AllocatedOutboundPorts* on its load balancer to `0`, which enables [automatic outbound port assignment based on backend pool size][azure-lb-outbound-preallocatedports] when creating a cluster. For example, if a cluster has 50 or fewer nodes, 1024 ports are allocated to each node. As the number of nodes in the cluster increases, fewer ports are available per node.
320
320
321
321
> [!IMPORTANT]
322
-
> There is a hard limit of 1024 ports regardless of whether front-end IPs are added when the node size is less than 50.
322
+
> There is a hard limit of 1024 ports regardless of whether front-end IPs are added when the node size is less than or equal to 50 (1-50).
323
323
324
324
To show the *AllocatedOutboundPorts* value for the AKS cluster load balancer, use `az network lb outbound-rule list`.
Copy file name to clipboardExpand all lines: articles/app-service/environment/upgrade-to-asev3.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
@@ -4,7 +4,7 @@ description: Take the first steps toward upgrading to App Service Environment v3
4
4
ms.author: jordanselig
5
5
author: seligj95
6
6
ms.topic: overview
7
-
ms.date: 06/26/2023
7
+
ms.date: 07/17/2023
8
8
---
9
9
10
10
# Upgrade to App Service Environment v3
@@ -23,7 +23,7 @@ This page is your one-stop shop for guidance and resources to help you upgrade s
23
23
|**2**|**Migrate**|Based on results of your review, either upgrade using the migration feature or follow the manual steps.<br><br>- [Use the automated migration feature](how-to-migrate.md)<br>- [Migrate manually](migration-alternatives.md)|
24
24
|**3**|**Testing and troubleshooting**|Upgrading using the automated migration feature requires a 3-6 hour service window. Support teams are monitoring upgrades to ensure success. If you have a support plan and you need technical help, create a [support request](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest).|
25
25
|**4**|**Optimize your App Service plans**|Once your upgrade is complete, you can optimize the App Service plans for additional benefits.<br><br>Review the autoselected Isolated v2 SKU sizes and scale up or scale down your App Service plans as needed.<br><br>- [Scale down your App Service plans](../manage-scale-up.md)<br>- [App Service Environment post-migration scaling guidance](migrate.md#pricing)<br><br>Check out the pricing estimates if needed.<br><br>- [App Service pricing page](https://azure.microsoft.com/pricing/details/app-service/windows/)<br>- [Azure pricing calculator](https://azure.microsoft.com/pricing/calculator)|
26
-
|**5**|**Learn more**|Need more help? [Submit a request](https://cxp.azure.com/nominationportal/nominationform/fasttrack) to contact FastTrack.<br><br>[Frequently asked questions](migrate.md#frequently-asked-questions)<br><br>[Community support](https://aka.ms/asev1v2retirement)|
26
+
|**5**|**Learn more**|Join the [free live webinar](https://developer.microsoft.com/en-us/reactor/events/20417) with FastTrack Architects.<br><br>Need more help? [Submit a request](https://cxp.azure.com/nominationportal/nominationform/fasttrack) to contact FastTrack.<br><br>[Frequently asked questions](migrate.md#frequently-asked-questions)<br><br>[Community support](https://aka.ms/asev1v2retirement)|
:::image type="content" source="./media/preview-features/subscriptions.png" alt-text="Screenshot of Azure portal with subscription selection highlighted.":::
38
38
39
39
1. From the left menu, under **Settings** select **Preview features**.
40
40
41
-
:::image type="content" source="./media/preview-features/preview-features-menu.png" alt-text="Azure preview features menu.":::
41
+
:::image type="content" source="./media/preview-features/preview-features-menu.png" alt-text="Screenshot of Azure portal with Preview features menu option highlighted.":::
42
42
43
43
1. You see a list of available preview features and your current registration status.
44
44
45
-
:::image type="content" source="./media/preview-features/preview-features-list.png" alt-text="Azure portal list of preview features.":::
45
+
:::image type="content" source="./media/preview-features/preview-features-list.png" alt-text="Screenshot of Azure portal displaying a list of preview features.":::
46
46
47
47
1. From **Preview features** you can filter the list by **name**, **State**, or **Type**:
48
48
49
49
-**Filter by name**: Must contain text from a preview feature's name, not the **Display name**.
50
50
-**State**: Select the drop-down menu and choose a state. The portal doesn't filter by **Unregistered**.
51
51
-**Type**: Select the drop-down menu and choose a type.
:::image type="content" source="./media/preview-features/filter.png" alt-text="Screenshot of Azure portal with filter options for preview features.":::
54
54
55
55
# [Azure CLI](#tab/azure-cli)
56
56
@@ -169,7 +169,7 @@ Some services require other methods, such as email, to get approval for pending
169
169
1. Select the link for the preview feature you want to register.
:::image type="content" source="./media/preview-features/register.png" alt-text="Screenshot of Azure portal with Register button for a preview feature.":::
173
173
174
174
1. Select **OK**.
175
175
@@ -253,7 +253,7 @@ You can unregister preview features from **Preview features**. The **State** cha
253
253
1. Select the link for the preview feature you want to unregister.
:::image type="content" source="./media/preview-features/unregister.png" alt-text="Screenshot of Azure portal with Unregister button for a preview feature.":::
Copy file name to clipboardExpand all lines: articles/azure-resource-manager/management/request-limits-and-throttling.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
@@ -13,7 +13,7 @@ Throttling happens at two levels. Azure Resource Manager throttles requests for
13
13
14
14
The following image shows how throttling is applied as a request goes from the user to Azure Resource Manager and the resource provider. The image shows that requests are initially throttled per principal ID and per Azure Resource Manager instance in the region of the user sending the request. The requests are throttled per hour. When the request is forwarded to the resource provider, requests are throttled per region of the resource rather than per Azure Resource Manager instance in region of the user. The resource provider requests are also throttled per principal user ID and per hour.
:::image type="content" source="./media/request-limits-and-throttling/request-throttling.svg" alt-text="Diagram that shows how throttling is applied as a request goes from the user to Azure Resource Manager and the resource provider.":::
0 commit comments