Merge pull request #228488 from MicrosoftDocs/main

2/24 AM Publish

Author: huypub

articles/active-directory/cloud-infrastructure-entitlement-management/partner-list.md

@@ -31,7 +31,7 @@ Microsoft verified partners can help you onboard Microsoft Entra Permissions Man
 * **Onboarding and Deployment Support**
 
     Partners can guide you through the entire onboarding and deployment process for 
-    ermissions Management across AWS, Azure, and GCP.
+    Permissions Management across AWS, Azure, and GCP.
 
 
 ## Partner list

articles/active-directory/conditional-access/concept-conditional-access-grant.md

@@ -94,7 +94,6 @@ To apply this grant control, the device must be registered in Azure AD, which re
 The following client apps support this setting, this list isn't exhaustive and is subject to change::
 
 - Microsoft Azure Information Protection
-- Microsoft Bookings
 - Microsoft Cortana
 - Microsoft Dynamics 365
 - Microsoft Edge
@@ -114,7 +113,6 @@ The following client apps support this setting, this list isn't exhaustive and i
 - Microsoft PowerPoint
 - Microsoft SharePoint
 - Microsoft Skype for Business
-- Microsoft StaffHub
 - Microsoft Stream
 - Microsoft Teams
 - Microsoft To-Do

articles/active-directory/conditional-access/location-condition.md

@@ -1,6 +1,6 @@
 ---
 title: Location condition in Azure Active Directory Conditional Access
-description: Use the location condition to control access based on user physical or network location.
+description: Learn about creating location-based Conditional Access policies using Azure AD.
 
 services: active-directory
 ms.service: active-directory

articles/active-directory/fundamentals/active-directory-faq.yml

@@ -10,7 +10,7 @@ metadata:
   ms.subservice: fundamentals
   ms.workload: identity
   ms.topic: faq
-  ms.date: 08/17/2022
+  ms.date: 02/15/2023
   ms.author: barclayn
   ms.custom: "it-pro, seodec18"
   ms.collection: M365-identity-device-management
@@ -73,7 +73,7 @@ sections:
       - question: |
           How do I leave a tenant when I'm added as a collaborator?
         answer: |
-          When you are added to another organization's tenant as a collaborator, you can use the "tenant switcher" in the upper right to switch between tenants.  Currently, there is no way to leave the inviting organization, and Microsoft is working on providing this functionality.  Until this feature is available, you can ask the inviting organization to remove you from their tenant.
+         Information on how to leave tenants where you were added as a collaborator is documented in [Leave an organization as an external user](../external-identities/leave-the-organization.md)
           
           
           

articles/active-directory/fundamentals/users-default-permissions.md

@@ -9,7 +9,7 @@ ms.service: active-directory
 ms.subservice: fundamentals
 ms.workload: identity
 ms.topic: conceptual
-ms.date: 02/13/2023
+ms.date: 02/17/2023
 ms.author: barclayn
 ms.reviewer: vincesm
 ms.custom: "it-pro, seodec18, contperf-fy21q1"
@@ -78,8 +78,6 @@ Permission | Setting explanation
 ---------- | ------------
 **Guest user access restrictions** | Setting this option to **Guest users have the same access as members** grants all member user permissions to guest users by default.<p>Setting this option to **Guest user access is restricted to properties and memberships of their own directory objects** restricts guest access to only their own user profile by default. Access to other users is no longer allowed, even when they're searching by user principal name, object ID, or display name. Access to group information, including groups memberships, is also no longer allowed.<p>This setting doesn't prevent access to joined groups in some Microsoft 365 services like Microsoft Teams. To learn more, see [Microsoft Teams guest access](/MicrosoftTeams/guest-access).<p>Guest users can still be added to administrator roles regardless of this permission setting.
 **Guests can invite** | Setting this option to **Yes** allows guests to invite other guests. To learn more, see [Configure external collaboration settings](../external-identities/external-collaboration-settings-configure.md).
-**Members can invite** | Setting this option to **Yes** allows non-admin members of your directory to invite guests. To learn more, see [Configure external collaboration settings](../external-identities/external-collaboration-settings-configure.md).
-**Admins and users in the guest inviter role can invite** | Setting this option to **Yes** allows admins and users in the guest inviter role to invite guests. When you set this option to **Yes**, users in the guest inviter role will still be able to invite guests, regardless of the **Members can invite** setting. To learn more, see [Configure external collaboration settings](../external-identities/external-collaboration-settings-configure.md).
 
 ## Object ownership
 

articles/active-directory/governance/customize-workflow-schedule.md

@@ -14,31 +14,30 @@ ms.reviewer: krbain
 ms.collection: M365-identity-device-management
 ---
 
-# Customize the schedule of workflows (Preview)
+# Customize the schedule of workflows
 
 Workflows created using Lifecycle Workflows can be fully customized to match the schedule that fits your organization's needs. By default, workflows are scheduled to run every 3 hours, but the interval can be set as frequent as 1 hour, or as infrequent as 24 hours.
 
 
-## Customize the schedule of workflows using Microsoft Graph
+## Customize the schedule of workflows using the Azure portal
+
+Workflows created within Lifecycle Workflows follow the same schedule that you define within the **Workflow Settings** page. To adjust the schedule, you'd follow these steps:
 
+1. Sign in to the [Azure portal](https://portal.azure.com).
 
-First, to view the current schedule interval of your workflows, run the following get call:
+1. Select **Identity Governance** on the search bar near the top of the page.
 
-```http
-GET https://graph.microsoft.com/beta/identityGovernance/lifecycleWorkflows/settings
-```
+1. In the left menu, select **Lifecycle workflows (Preview)**.
 
+1. Select **Workflow settings (Preview)** from the Lifecycle workflows overview page.
 
-To customize a workflow in Microsoft Graph, use the following request and body:
-```http
-PATCH https://graph.microsoft.com/beta/identityGovernance/lifecycleWorkflows/settings
-Content-type: application/json
+1. On the workflow settings page you can set the schedule of workflows from an interval between 1-24.
+    :::image type="content" source="media/customize-workflow-schedule/workflow-schedule-settings.png" alt-text="Screenshot of the settings for workflow schedule.":::
+1. After setting the workflow schedule, select save.
 
-{
-"workflowScheduleIntervalInHours":<Interval between 0-24>
-}
+## Customize the schedule of workflows using Microsoft Graph
 
-```
+To schedule workflow settings using API via Microsoft Graph, see: Update lifecycleManagementSettings [tenant settings for Lifecycle Workflows](/graph/api/resources/identitygovernance-lifecyclemanagementsettings).
 
 ## Next steps
 

articles/active-directory/governance/media/customize-workflow-schedule/workflow-schedule-settings.png

@@ -12,7 +12,7 @@ ms.subservice: msi
 ms.topic: how-to
 ms.tgt_pltfrm: na
 ms.workload: identity
-ms.date: 01/11/2022
+ms.date: 02/15/2022
 ms.author: barclayn
 ms.collection: M365-identity-device-management 
 ms.custom: devx-track-azurepowershell
@@ -39,7 +39,7 @@ In this article, you learn how to view the service principal of a managed identi
 
 This following command demonstrates how to view the service principal of a VM or application with system assigned identity enabled. Replace `<Azure resource name>` with your own values.
 
-```azurepowershell-interactive
+```powershell
 Get-AzADServicePrincipal -DisplayName <Azure resource name>
 ```
 

articles/active-directory/managed-identities-azure-resources/how-to-view-managed-identity-service-principal-powershell.md

@@ -233,7 +233,7 @@ Starting with version 1.2.0, Azure CNI sets Transparent mode as default for sing
 
 ### Bridge mode
 
-As the name suggests, bridge mode Azure CNI, in a "just in time" fashion, will create a L2 bridge named "azure0". All the host side pod `veth` pair interfaces will be connected to this bridge. So Pod-Pod intra VM communication and the remaining traffic goes through this bridge. The bridge in question is a layer 2 virtual device that on its own cannot receive or transmit anything unless you bind one or more real devices to it. For this reason, eth0 of the Linux VM has to be converted into a subordinate to "azure0" bridge. This creates a complex network topology within the Linux VM and as a symptom CNI had to take care of other networking functions like DNS server update and so on.
+As the name suggests, bridge mode Azure CNI, in a "just in time" fashion, will create an L2 bridge named "azure0". All the host side pod `veth` pair interfaces will be connected to this bridge. So Pod-Pod intra VM communication and the remaining traffic goes through this bridge. The bridge in question is a layer 2 virtual device that on its own cannot receive or transmit anything unless you bind one or more real devices to it. For this reason, eth0 of the Linux VM has to be converted into a subordinate to "azure0" bridge. This creates a complex network topology within the Linux VM and as a symptom CNI had to take care of other networking functions like DNS server update and so on.
 
 :::image type="content" source="media/faq/bridge-mode.png" alt-text="Bridge mode topology":::
 

articles/aks/faq.md

@@ -18,6 +18,7 @@ The following Microsoft-provided Kubernetes distributions and infrastructure pro
 | Cluster API Provider on Azure            | Release version: [0.4.12](https://github.com/kubernetes-sigs/cluster-api-provider-azure/releases/tag/v0.4.12); Kubernetes version: [1.18.2](https://github.com/kubernetes/kubernetes/releases/tag/v1.18.2) |
 | AKS on Azure Stack HCI                   | Release version: [December 2020 Update](https://github.com/Azure/aks-hci/releases/tag/AKS-HCI-2012); Kubernetes version: [1.18.8](https://github.com/kubernetes/kubernetes/releases/tag/v1.18.8) |
 | K8s on Azure Stack Edge                  | Release version: Azure Stack Edge 2207 (2.2.2037.5375); Kubernetes version: [1.22.6](https://github.com/kubernetes/kubernetes/releases/tag/v1.22.6) |
+| AKS Edge Essentials                  | Release version [1.0.406.0]( https://github.com/Azure/AKS-Edge/releases/tag/1.0.406.0); Kubernetes version [1.24.3](https://github.com/kubernetes/kubernetes/releases/tag/v1.24.3) |
 
 The following providers and their corresponding Kubernetes distributions have successfully passed the conformance tests for Azure Arc-enabled Kubernetes: