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/governance/workflows-faqs.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,6 +23,9 @@ In this article you will find questions to commonly asked questions about [Lifec
23
23
24
24
Yes, custom workflows can be configured for members or guests in your tenant. Workflows can run for all types of external guests, external members, internal guests and internal members.
25
25
26
+
### Why do I see "Lifecycle Management" instead of "Lifecycle Workflows"?
27
+
For a small portion of our customers, Lifecycle Workflows may still be listed under the former name Lifecycle Management in the audit logs and enterprise applications.
28
+
26
29
### Do I need to map employeeHireDate in provisioning apps like WorkDay?
27
30
28
31
Yes, key user properties like employeeHireDate and employeeType are supported for user provisioning from HR apps like WorkDay. To use these properties in Lifecycle workflows, you will need to map them in the provisioning process to ensure the values are set. The following is an example of the mapping:
Copy file name to clipboardExpand all lines: articles/active-directory/hybrid/how-to-connect-modify-group-writeback.md
+24-5Lines changed: 24 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,7 +28,7 @@ This article walks you through the options for modifying the default behaviors o
28
28
29
29
If the original version of group writeback is already enabled and in use in your environment, all your Microsoft 365 groups have already been written back to Active Directory. Instead of disabling all Microsoft 365 groups, review any use of the previously written-back groups. Disable only those that are no longer needed in on-premises Active Directory.
30
30
31
-
### Disable automatic writeback of all Microsoft 365 groups
31
+
### Disable automatic writeback of new Microsoft 365 groups
32
32
33
33
To configure directory settings to disable automatic writeback of newly created Microsoft 365 groups, use one of these methods:
34
34
@@ -45,13 +45,32 @@ To configure directory settings to disable automatic writeback of newly created
45
45
46
46
- Microsoft Graph: Use the [directorySetting](/graph/api/resources/directorysetting?view=graph-rest-beta&preserve-view=true) resource type.
47
47
48
-
### Disable writeback for each existing Microsoft 365 group
48
+
### Disable writeback for all existing Microsoft 365 group
49
+
50
+
To disable writeback of all Microsoft 365 groups that were created before these modifications, use one of the folowing methods:
49
51
50
52
- Portal: Use the [Microsoft Entra admin portal](../enterprise-users/groups-write-back-portal.md).
51
-
- PowerShell: Use the [Microsoft Identity Tools PowerShell module](https://www.powershellgallery.com/packages/MSIdentityTools/2.0.16). For example:
53
+
- PowerShell: Use the [Microsoft Graph PowerShell SDK](/powershell/microsoftgraph/installation?view=graph-powershell-1.0&preserve-view=true). For example:
54
+
55
+
```PowerShell
56
+
#Import-module
57
+
Import-module Microsoft.Graph
58
+
59
+
#Connect to MgGraph and select the Beta API Version
> We recomend using Microsoft Graph PowerShell SDK with [Windows PowerShell 7](/powershell/scripting/whats-new/migrating-from-windows-powershell-51-to-powershell-7?view=powershell-7.3&preserve-view=true)
Copy file name to clipboardExpand all lines: articles/aks/certificate-rotation.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
@@ -75,7 +75,7 @@ For any AKS clusters created or upgraded after March 2022 Azure Kubernetes Servi
75
75
76
76
To verify if TLS Bootstrapping is enabled on your cluster browse to the following paths:
77
77
78
-
* On a Linux node: */var/lib/kubelet/bootstrap-kubeconfig*
78
+
* On a Linux node: */var/lib/kubelet/bootstrap-kubeconfig* or */host/var/lib/kubelet/bootstrap-kubeconfig*
79
79
* On a Windows node: *C:\k\bootstrap-config*
80
80
81
81
To access agent nodes, see [Connect to Azure Kubernetes Service cluster nodes for maintenance or troubleshooting][aks-node-access] for more information.
Copy file name to clipboardExpand all lines: articles/api-management/api-management-howto-ip-addresses.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -128,6 +128,7 @@ In the Developer, Basic, Standard, and Premium tiers of API Management, the publ
128
128
* The service subscription is [suspended](https://github.com/Azure/azure-resource-manager-rpc/blob/master/v1.0/subscription-lifecycle-api-reference.md#subscription-states) or [warned](https://github.com/Azure/azure-resource-manager-rpc/blob/master/v1.0/subscription-lifecycle-api-reference.md#subscription-states) (for example, for nonpayment) and then reinstated.
129
129
* (Developer and Premium tiers) Azure Virtual Network is added to or removed from the service.
130
130
* (Developer and Premium tiers) API Management service is switched between external and internal VNet deployment mode.
131
+
* (Developer and Premium tiers) API Management service is moved to a different subnet.
131
132
* (Premium tier) [Availability zones](../reliability/migrate-api-mgt.md) are enabled, added, or removed.
132
133
* (Premium tier) In [multi-regional deployments](api-management-howto-deploy-multi-region.md), the regional IP address changes if a region is vacated and then reinstated.
0 commit comments