Merge pull request #227979 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: huypub

articles/active-directory/governance/how-to-lifecycle-workflow-sync-attributes.md

@@ -78,7 +78,7 @@ For more attributes, see the [Workday attribute reference](../app-provisioning/w
 
 
 ## Importance of time
-To ensure timing accuracy of scheduled workflows it’s curial to consider:
+To ensure timing accuracy of scheduled workflows it’s crucial to consider:
 
 - The time portion of the attribute must be set accordingly, for example the `employeeHireDate` should have a time at the beginning of the day like 1AM or 5AM and the `employeeLeaveDateTime` should have time at the end of the day like 9PM or 11PM
 - The Workflows won't run earlier than the time specified in the attribute, however the [tenant schedule (default 3h)](customize-workflow-schedule.md) may delay the workflow run.  For instance, if you set the `employeeHireDate` to 8AM but the tenant schedule doesn't run until 9AM, the workflow won't be processed until then.  If a new hire is starting at 8AM, you would want to set the time to something like (start time - tenant schedule) to ensure it had run before the employee arrives.

articles/azure-monitor/overview.md

@@ -16,7 +16,7 @@ Azure Monitor collects and aggregates the data from every layer and component of
 
 Azure Monitor also includes Azure Monitor SCOM Managed Instance, which allows you to move your on-premises System Center Operation Manager (Operations Manager) installation to the cloud in Azure.
 
-Use Azure Monitor to monitor these types resources in Azure, other clouds, or on-premises: 
+Use Azure Monitor to monitor these types of resources in Azure, other clouds, or on-premises: 
   - Applications 
   - Virtual machines
   - Guest operating systems 
@@ -161,4 +161,4 @@ You may need to integrate Azure Monitor with other systems or to build custom so
 ## Next steps
 - [Getting started with Azure Monitor](getting-started.md)
 - [Sources of monitoring data for Azure Monitor](data-sources.md)
-- [Data collection in Azure Monitor](essentials/data-collection.md)
+- [Data collection in Azure Monitor](essentials/data-collection.md)

articles/defender-for-cloud/azure-devops-extension.md

@@ -111,6 +111,9 @@ If you don't have access to install the extension, you must request access from
       displayName: 'Microsoft Security DevOps'
     ```
 
+> [!Note] 
+> The MicrosoftSecurityDevOps build task depends on .NET 6. The CredScan analyzer depends on .NET 3.1. See more [here](https://marketplace.visualstudio.com/items?itemName=ms-securitydevops.microsoft-security-devops-azdevops).
+
 1. Select **Save and run**.
 
 1. To commit the pipeline, select **Save and run**.

articles/defender-for-cloud/github-action.md

@@ -87,7 +87,7 @@ Security DevOps uses the following Open Source tools:
 
             # Upload alerts to the Security tab
             - name: Upload alerts to Security tab
-              uses: github/codeql-action/upload-sarif@v1
+              uses: github/codeql-action/upload-sarif@v2
               with:
                 sarif_file: ${{ steps.msdo.outputs.sarifFile }}
     ```

articles/openshift/howto-add-update-pull-secret.md

@@ -131,12 +131,19 @@ This section walks through updating that pull secret with additional values from
 Run the following command to update your pull secret.
 
 > [!NOTE]
-> Running this command will cause your cluster nodes to restart one by one as they're updated.
+> In ARO 4.9 or older, running this command will cause your cluster nodes to restart one by one as they're updated.
+> In ARO 4.10 version or later a restart will not be triggered.
 
 ```console
 oc set data secret/pull-secret -n openshift-config --from-file=.dockerconfigjson=./pull-secret.json
 ```
 
+### Verify that pull secret is in place
+
+```
+oc exec $(oc get pod -n openshift-apiserver -o jsonpath="{.items[0].metadata.name}") -- cat /var/lib/kubelet/config.json
+```
+
 After the secret is set, you're ready to enable Red Hat Certified Operators.
 
 ### Modify the configuration files

articles/virtual-desktop/publish-apps.md

@@ -32,7 +32,7 @@ To publish a built-in app:
        CommandLineSetting = '<Allow|Require|DoNotAllow>'
        IconIndex = '0'
        IconPath = '<IconPath>'
-       howInPortal = $true
+       ShowInPortal = $true
     }
 
    New-AzWvdApplication @parameters
@@ -58,7 +58,7 @@ $parameters = @{
     CommandLineSetting = '<Allow|Require|DoNotAllow>'
     IconIndex = '0'
     IconPath = 'C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\microsoftedge'
-    howInPortal = $true
+    ShowInPortal = $true
 }
 
 New-AzWvdApplication @parameters