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/conditional-access/concept-conditional-access-cloud-apps.md
+28-18Lines changed: 28 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -82,23 +82,33 @@ Administrators can exclude specific apps from policy if they wish, including the
82
82
83
83
The following key applications are included in the Office 365 client app:
84
84
85
-
- Microsoft Forms
86
-
- Microsoft Planner
87
-
- Microsoft Stream
88
-
- Microsoft To-Do
89
-
- Microsoft Teams
90
-
- Exchange Online
91
-
- SharePoint Online
92
-
- Microsoft 365 Search Service
93
-
- Yammer
94
-
- Office Delve
95
-
- Office Online
96
-
- Office.com
97
-
- OneDrive
98
-
- Power Automate
99
-
- Power Apps
100
-
- Skype for Business Online
101
-
- Sway
85
+
- Exchange Online
86
+
- Microsoft 365 Search Service
87
+
- Microsoft Forms
88
+
- Microsoft Planner (ProjectWorkManagement)
89
+
- Microsoft Stream
90
+
- Microsoft Teams
91
+
- Microsoft To-Do
92
+
- Microsoft Flow
93
+
- Microsoft Office 365 Portal
94
+
- Microsoft Office client application
95
+
- Microsoft Stream
96
+
- Microsoft To-Do WebApp
97
+
- Microsoft Whiteboard Services
98
+
- Office Delve
99
+
- Office Online
100
+
- Office.com
101
+
- OneDrive
102
+
- Power Apps
103
+
- Power Automate
104
+
- Security & Compliance Center
105
+
- SharePoint Online
106
+
- Skype for Business Online
107
+
- Skype and Teams Tenant Admin API
108
+
- Sway
109
+
- Yammer
110
+
111
+
A complete list of all services included can be found in the article [Apps included in Conditional Access Office 365 app suite](reference-office-365-application-contents.md).
102
112
103
113
### Microsoft Azure Management
104
114
@@ -192,4 +202,4 @@ For more information about authentication context use in applications, see the f
Copy file name to clipboardExpand all lines: articles/active-directory/verifiable-credentials/whats-new.md
+34-28Lines changed: 34 additions & 28 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,13 +26,18 @@ We are rolling out some important updates to our service that are breaking chang
26
26
- Azure AD Verifiable Credentials customers can take advantage of enhancements to credential revocation that add a higher degree of privacy through the implementation of the [W3C Status List 2021](https://w3c-ccg.github.io/vc-status-list-2021/) standard. [Read more](whats-new.md?#credential-revocation-with-enhanced-privacy)
27
27
28
28
>[!IMPORTANT]
29
-
> All Azure AD Verifiable Credential customers receiving a banner notice in the Azure portal need to go through a service reconfiguration before March 31st 2022. On March 31st 2022 tenants that have not been reconfigured will lose access to any previous configuration and will require to configure a new instance of the Azure AD Verifiable Credential service. Learn more about how to [reconfigure your tenant](verifiable-credentials-faq.md?#how-do-i-reconfigure-the-azure-ad-verifiable-credentials-service).
29
+
> All Azure AD Verifiable Credential customers receiving a banner notice in the Azure portal need to go through a service reconfiguration before March 31st 2022. On March 31st 2022 tenants that have not been reconfigured will lose access to any previous configuration. Administrators will have to set up a new instance of the Azure AD Verifiable Credential service. Learn more about how to [reconfigure your tenant](verifiable-credentials-faq.md?#how-do-i-reconfigure-the-azure-ad-verifiable-credentials-service).
30
30
31
31
### Azure AD Verifiable Credentials available in Europe
32
32
33
-
Since the Azure AD Verifiable Credentials service's Public Preview rollout, the service has been available in our Azure North America region. Now, the service is also available in our Azure European region. Customers with Azure AD tenants setup in Europe will have Verifiable Credentials data located and processed in our Azure Europe region. Customers with Azure AD tenants setup in Europe who start using the Azure AD Verifiable Credentials service after February 15, 2022, will automatically have their data processed in Europe and don't need to take any further actions. Customers with Azure AD tenants setup in Europe that started using the Azure AD Verifiable Credentials service before February 15, 2022, are required to reconfigure the service on their tenants before March 31, 2022.
33
+
Since the beginning of the Azure AD Verifiable Credentials service public preview, the service has only been available in our Azure North America region. Now, the service is also available in our Azure Europe region.
34
+
35
+
- Customers with Azure AD European tenants now have their Verifiable Credentials data located and processed in our Azure Europe region.
36
+
- Customers with Azure AD tenants setup in Europe who start using the Azure AD Verifiable Credentials service after February 15, 2022, have their data automatically processed in Europe and don't need to take any further actions.
37
+
- Customers with Azure AD tenants setup in Europe that started using the Azure AD Verifiable Credentials service before February 15, 2022, are required to reconfigure the service on their tenants before March 31, 2022.
34
38
35
39
Take the following steps to configure the Verifiable Credentials service in Europe:
40
+
36
41
1.[Check the location](verifiable-credentials-faq.md#how-can-i-check-my-azure-ad-tenants-region) of your Azure Active Directory to make sure is in Europe.
37
42
1.[Reconfigure the Verifiable Credentials service](verifiable-credentials-faq.md?#how-do-i-reconfigure-the-azure-ad-verifiable-credentials-service) in your tenant.
38
43
@@ -52,7 +57,7 @@ To confirm which endpoint you should use, we recommend checking your Azure AD te
52
57
53
58
### Credential Revocation with Enhanced Privacy
54
59
55
-
The Azure AD Verifiable Credential service supports the [W3C Status List 2021](https://w3c-ccg.github.io/vc-status-list-2021/) standard. Each Issuer tenant will have an [Identity Hub](https://identity.foundation/identity-hub/spec/) endpoint that is used by verifiers to check on the status of a credential using a privacy-respecting mechanism. The identity hub endpoint for the tenant is also published in the DID document. This feature replaces the current status endpoint.
60
+
The Azure AD Verifiable Credential service supports the [W3C Status List 2021](https://w3c-ccg.github.io/vc-status-list-2021/) standard. Each Issuer tenant now has an [Identity Hub](https://identity.foundation/identity-hub/spec/) endpoint used by verifiers to check on the status of a credential using a privacy-respecting mechanism. The identity hub endpoint for the tenant is also published in the DID document. This feature replaces the current status endpoint.
56
61
57
62
To uptake this feature follow the next steps:
58
63
1.[Check if your tenant has the Hub endpoint](verifiable-credentials-faq.md#how-can-i-check-if-my-tenant-has-the-new-hub-endpoint).
@@ -61,34 +66,35 @@ To uptake this feature follow the next steps:
61
66
1. Create new verifiable credentials contracts. In the rules file you must add the ` "credentialStatusConfiguration": "anonymous" ` property to start using the new feature in combination with the Hub endpoint for your credentials:
62
67
63
68
Sample contract file:
64
-
```json
65
-
{
66
-
"attestations": {
67
-
"idTokens": [
68
-
{
69
-
"id": "https://self-issued.me",
70
-
"mapping": {
71
-
"firstName": { "claim": "$.given_name" },
72
-
"lastName": { "claim": "$.family_name" }
73
-
},
74
-
"configuration": "https://self-issued.me",
75
-
"client_id": "",
76
-
"redirect_uri": ""
77
-
}
78
-
]
79
-
},
80
-
"validityInterval": 2592001,
81
-
"credentialStatusConfiguration": "anonymous",
82
-
"vc": {
83
-
"type": [ "VerifiedCredentialExpert" ]
84
-
}
85
-
}
86
-
```
69
+
70
+
```json
71
+
{
72
+
"attestations": {
73
+
"idTokens": [
74
+
{
75
+
"id": "https://self-issued.me",
76
+
"mapping": {
77
+
"firstName": { "claim": "$.given_name" },
78
+
"lastName": { "claim": "$.family_name" }
79
+
},
80
+
"configuration": "https://self-issued.me",
81
+
"client_id": "",
82
+
"redirect_uri": ""
83
+
}
84
+
]
85
+
},
86
+
"validityInterval": 2592001,
87
+
"credentialStatusConfiguration": "anonymous",
88
+
"vc": {
89
+
"type": [ "VerifiedCredentialExpert" ]
90
+
}
91
+
}
92
+
```
93
+
87
94
3. You have to issue new verifiable credentials using your new configuration. All verifiable credentials previously issued will continue to exist as your previous DID will remain resolvable however, they use the previous status endpoint implementation.
88
95
89
96
>[!IMPORTANT]
90
-
> Reconfiguring the Azure AD Verifiable Credentials service is required so that the new Identity Hub service endpoint can be created for the tenant. Tenants have until March 31st 2022, to schedule and manage the reconfiguration of the Verifiable Vredential service. On March 31st, 2022 tenants that have not been reconfigured will lose access to any previous configuration and will require to configure a new instance of the Azure AD Verifiable Credential service.
91
-
97
+
> You have to reconfigure your Azure AD Verifiable Credential service instance to create your new Identity hub endpoint. You have until March 31st 2022, to schedule and manage the reconfiguration of your deployment. On March 31st, 2022 deployments that have not been reconfigured will lose access to any previous Azure AD Verifiable Credentials service configuration. Administrators will need to set up a new service instance.
Copy file name to clipboardExpand all lines: articles/aks/use-multiple-node-pools.md
+31Lines changed: 31 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -348,6 +348,35 @@ az aks nodepool list -g myResourceGroup --cluster-name myAKSCluster
348
348
349
349
It takes a few minutes to delete the nodes and the node pool.
350
350
351
+
## Associate capacity reservation groups to node pools (preview)
352
+
353
+
[!INCLUDE [preview features callout](./includes/preview/preview-callout.md)]
354
+
355
+
As your application workloads demands, you may associate node pools to capacity reservation groups created prior. This ensures guaranteed capacity is allocated for your node pools.
356
+
357
+
For more information on the capacity reservation groups, please refer to [Capacity Reservation Groups][capacity-reservation-groups].
358
+
359
+
Associating a node pool with an existing capacity reservation group can be done using [az aks nodepool add][az-aks-nodepool-add] command and specifying a capacity reservation group with the --capacityReservationGroup flag" The capacity reservation group should already exist , otherwise the node pool will be added to the cluster with a warning and no capacity reservation group gets associated.
360
+
361
+
```azurecli-interactive
362
+
az aks nodepool add -g MyRG --cluster-name MyMC -n myAP --capacityReservationGroup myCRG
363
+
```
364
+
Associating a system node pool with an existing capacity reservation group can be done using [az aks create][az-aks-create] command. If the capacity reservation group specified does not exist, then a warning is issued and the cluster gets created without any capacity reservation group association.
365
+
366
+
```azurecli-interactive
367
+
az aks create -g MyRG --cluster-name MyMC --capacityReservationGroup myCRG
368
+
```
369
+
Deleting a node pool command will implicitly dissociate a node pool from any associated capacity reservation group, before that node pool is deleted.
370
+
371
+
```azurecli-interactive
372
+
az aks nodepool delete -g MyRG --cluster-name MyMC -n myAP
373
+
```
374
+
Deleting a cluster command implicitly dissociates all node pools in a cluster from their associated capacity reservation groups.
375
+
376
+
```azurecli-interactive
377
+
az aks delete -g MyRG --cluster-name MyMC
378
+
```
379
+
351
380
## Specify a VM size for a node pool
352
381
353
382
In the previous examples to create a node pool, a default VM size was used for the nodes created in the cluster. A more common scenario is for you to create node pools with different VM sizes and capabilities. For example, you may create a node pool that contains nodes with large amounts of CPU or memory, or a node pool that provides GPU support. In the next step, you [use taints and tolerations](#setting-nodepool-taints) to tell the Kubernetes scheduler how to limit access to pods that can run on these nodes.
@@ -843,6 +872,7 @@ Use [proximity placement groups][reduce-latency-ppg] to reduce latency for your
0 commit comments