Merge pull request #95263 from MicrosoftDocs/repo_sync_working_branch

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

Author: tfosmark

articles/active-directory/authentication/howto-mfa-getstarted.md

@@ -206,6 +206,9 @@ function Set-MfaState {
 Get-MsolUser -All | Set-MfaState -State Disabled
 ```
 
+> [!NOTE]
+> We recently changed the behavior and PowerShell script above accordingly. Previously, the script saved off the MFA methods, disabled MFA, and restored the methods. This is no longer necessary now that the default behavior for disable doesn't clear the methods.
+
 ## Plan Conditional Access policies
 
 To plan your Conditional Access policy strategy, which will determine when MFA and other controls are required, refer to [What is Conditional Access in Azure Active Directory?](../conditional-access/overview.md).

articles/active-directory/hybrid/how-to-connect-staged-rollout.md

@@ -113,16 +113,16 @@ Enable Seamless SSO on the AD forests using PowerShell. If you have more than
 
 2. Navigate to the %programfiles%\\Microsoft Azure Active Directory Connect folder.
 
-3. Import the Seamless SSO PowerShell module using this command: `Import-Module .\\AzureADSSO.psd1`.
+3. Import the Seamless SSO PowerShell module using this command: `Import-Module .\AzureADSSO.psd1`.
 
 4. Run PowerShell as an Administrator. In PowerShell, call `New-AzureADSSOAuthenticationContext`. This command should give you a dialog box where you can enter your tenant's Global Administrator credentials.
 
-5. Call `Get-AzureADSSOStatus|ConvertFrom-Json`. This command provides you the list of AD forests (look at the \"Domains\" list) on which this feature has been enabled. By default, it is set to false at the tenant level.
+5. Call `Get-AzureADSSOStatus | ConvertFrom-Json`. This command provides you the list of AD forests (look at the \"Domains\" list) on which this feature has been enabled. By default, it is set to false at the tenant level.
 
    > **Example:**
    > ![Example of the Windows PowerShell output](./media/how-to-connect-staged-rollout/sr3.png)
 
-6. Call `$creds=Get-Credential`. When prompted, enter the Domain Administrator credentials for the intended AD forest.
+6. Call `$creds = Get-Credential`. When prompted, enter the Domain Administrator credentials for the intended AD forest.
 
 7. Call `Enable-AzureADSSOForest -OnPremCredentials $creds`. This command creates the AZUREADSSOACC computer account from the on-premises domain controller for this specific Active Directory forest that is required for Seamless SSO.
 

articles/active-directory/hybrid/reference-connect-sync-attributes-synchronized.md

@@ -59,7 +59,7 @@ In this case, start with the list of attributes in this topic and identify those
 | company |X |X | | |
 | countryCode |X |X | | |
 | department |X |X | | |
-| description |X |X |X | |
+| description | | |X | |
 | displayName |X |X |X | |
 | dLMemRejectPerms |X |X |X | |
 | dLMemSubmitPerms |X |X |X | |

articles/active-directory/hybrid/reference-connect-version-history.md

@@ -75,8 +75,8 @@ Under certain circumstances, servers that were auto upgraded to version 1.4.18.0
 - Added a deprecation warning for the sync service manager on the connector properties page. This warning notifies the user that changes should be made through the AADC wizard.
 - Added new error for issues with a user's password policy.
 - Prevent misconfiguration of  group filtering by domain and OU filters. Group filtering will show an error when the domain/OU of the entered group is already filtered out and keep the user from moving forward until the issue is resolved.
-- Users can no longer create a connector for Active Directory Domain Services or Windows Azure Active Directory in the old UI.
-- Fixed accessibility of custom UI controls in the Sync Service Manager
+- Users can no longer create a connector for Active Directory Domain Services or Windows Azure Active Directory in the Synchronization Service Manager UI.
+- Fixed accessibility of custom UI controls in the Synchronization Service Manager.
 - Enabled six federation management tasks for all sign-in methods in Azure AD Connect.  (Previously, only the “Update AD FS SSL certificate” task was available for all sign-ins.)
 - Added a warning when changing the sign-in method from federation to PHS or PTA that all Azure AD domains and users will be converted to managed authentication.
 - Removed token-signing certificates from the “Reset Azure AD and AD FS trust” task and added a separate sub-task to update these certificates.
@@ -128,7 +128,7 @@ Under certain circumstances, servers that were auto upgraded to version 1.4.18.0
 - Add support for Domain Refresh 
 - Exchange Mail Public Folders feature goes GA 
 - Improve wizard error handling for service failures 
-- Added warning link for old UI on connector properties page. 
+- Added warning link on Synchronization Service Manager UI in the connector properties page. 
 - The Unified Groups Writeback feature is now GA 
 - Improved SSPR error message when the DC is missing an LDAP control 
 - Added diagnostics for DCOM registry errors during install  
@@ -154,7 +154,7 @@ Under certain circumstances, servers that were auto upgraded to version 1.4.18.0
 - Fix VSS Errors with LocalDB  
 - Fix misleading error message when object type is not in scope 
 - Corrected an issue where installation of Azure AD PowerShell on a server could potentially cause an assembly conflict with Azure AD Connect. 
-- Fixed PHS bug on Staging Server when Connector Credentials are updated in the old UI. 
+- Fixed PHS bug on Staging Server when Connector Credentials are updated in the Synchronization Service Manager UI. 
 - Fixed some memory leaks 
 - Miscellaneous Autoupgrade fixes 
 - Miscellaneous fixes to Export and Unconfirmed Import Processing 

articles/aks/azure-disks-dynamic-pv.md

@@ -38,7 +38,7 @@ Each AKS cluster includes two pre-created storage classes, both configured to wo
 * The *managed-premium* storage class provisions a premium Azure disk.
     * Premium disks are backed by SSD-based high-performance, low-latency disk. Perfect for VMs running production workload. If the AKS nodes in your cluster use premium storage, select the *managed-premium* class.
 
-These default storage classes don't allow you to update the volume size once created. To enable this ability, add the *allowVolumeExpansion: true* line to one of the default storage classes, or create you own custom storage class. You can edit an existing storage class using the `kubectl edit sc` command. For more information on storage classes and creating youor own, see [Storage options for applications in AKS][storage-class-concepts].
+These default storage classes don't allow you to update the volume size once created. To enable this ability, add the *allowVolumeExpansion: true* line to one of the default storage classes, or create you own custom storage class. You can edit an existing storage class using the `kubectl edit sc` command. For more information on storage classes and creating your own, see [Storage options for applications in AKS][storage-class-concepts].
 
 Use the [kubectl get sc][kubectl-get] command to see the pre-created storage classes. The following example shows the pre-create storage classes available within an AKS cluster:
 

articles/app-service/overview-managed-identity.md

@@ -38,7 +38,7 @@ To set up a managed identity in the portal, you will first create an application
 
 2. If using a function app, navigate to **Platform features**. For other app types, scroll down to the **Settings** group in the left navigation.
 
-3. Select **Managed identity**.
+3. Select **Identity**.
 
 4. Within the **System assigned** tab, switch **Status** to **On**. Click **Save**.
 
@@ -165,7 +165,7 @@ First, you'll need to create a user-assigned identity resource.
 
 3. If using a function app, navigate to **Platform features**. For other app types, scroll down to the **Settings** group in the left navigation.
 
-4. Select **Managed identity**.
+4. Select **Identity**.
 
 5. Within the **User assigned** tab, click **Add**.
 
@@ -190,7 +190,7 @@ Any resource of type `Microsoft.Web/sites` can be created with an identity by in
 > [!NOTE] 
 > An application can have both system-assigned and user-assigned identities at the same time. In this case, the `type` property would be `SystemAssigned,UserAssigned`
 
-Adding the user-assigned type and a cotells Azure to create and manage the identity for your application.
+Adding the user-assigned type tells Azure to use the user-assigned identity specified for your application.
 
 For example, a web app might look like the following:
 ```json

articles/azure-monitor/app/api-filtering-sampling.md

@@ -21,11 +21,11 @@ You can write and configure plug-ins for the Application Insights SDK to customi
 
 Before you start:
 
-* Install the appropriate SDK for your application: [ASP.NET](asp-net.md), [ASP.NET Core](asp-net-core.md), [Non HTTP/Worker for .NET/.NET Core](worker-service.md), or [Java](../../azure-monitor/app/java-get-started.md).
+* Install the appropriate SDK for your application: [ASP.NET](asp-net.md), [ASP.NET Core](asp-net-core.md), [Non HTTP/Worker for .NET/.NET Core](worker-service.md), [Java](../../azure-monitor/app/java-get-started.md) or [JavaScript](javascript.md)
 
 <a name="filtering"></a>
 
-## Filtering: ITelemetryProcessor
+## Filtering
 
 This technique gives you direct control over what is included or excluded from the telemetry stream. Filtering can be used to drop telemetry items from being sent to Application Insights. You can use it in conjunction with Sampling, or separately.
 
@@ -195,7 +195,30 @@ public void Process(ITelemetry item)
 
 <a name="add-properties"></a>
 
-## Add properties: ITelemetryInitializer
+### JavaScript Web applications
+
+**Filtering using ITelemetryInitializer**
+
+1. Create a telemetry initializer callback function. The callback function takes `ITelemetryItem` as a parameter, which is the event that is being processed. Returning `false` from this callback results in the telemetry item to be filtered out.  
+
+   ```JS
+   var filteringFunction = (envelope) => {
+     if (envelope.data.someField === 'tobefilteredout') {
+     	return false;
+     }
+  
+     return true;
+   };
+   ```
+
+2. Add your telemetry initializer callback:
+
+   ```JS
+   appInsights.addTelemetryInitializer(filteringFunction);
+   ```
+
+## Add/modify properties: ITelemetryInitializer
+
 
 Use telemetry initializers to enrich telemetry with additional information and/or to override telemetry properties set by the standard telemetry modules.
 

articles/azure-monitor/platform/gateway.md

@@ -22,7 +22,7 @@ The Log Analytics gateway is an HTTP forward proxy that supports HTTP tunneling
 
 The Log Analytics gateway supports:
 
-* Reporting up to the same four Log Analytics workspace agents that are behind it and that are configured with Azure Automation Hybrid Runbook Workers.  
+* Reporting up to the same Log Analytics workspaces configured on each agent behind it and that are configured with Azure Automation Hybrid Runbook Workers.  
 * Windows computers on which the Microsoft Monitoring Agent is directly connected to a Log Analytics workspace in Azure Monitor.
 * Linux computers on which a Log Analytics agent for Linux is directly connected to a Log Analytics workspace in Azure Monitor.  
 * System Center Operations Manager 2012 SP1 with UR7, Operations Manager 2012 R2 with UR3, or a management group in Operations Manager 2016 or later that is integrated with Log Analytics.  
@@ -383,4 +383,4 @@ To get help, select the question mark icon in the upper-right corner of the port
 
 ## Next steps
 
-[Add data sources](../../azure-monitor/platform/agent-data-sources.md) to collect data from connected sources, and store the data in your Log Analytics workspace.
+[Add data sources](../../azure-monitor/platform/agent-data-sources.md) to collect data from connected sources, and store the data in your Log Analytics workspace.

articles/event-hubs/event-hubs-dotnet-standard-getstarted-send.md

@@ -55,8 +55,8 @@ Add the [`Microsoft.Azure.EventHubs`](https://www.nuget.org/packages/Microsoft.A
 
     ```csharp
     using Microsoft.Azure.EventHubs;
-	using System.Text;
-	using System.Threading.Tasks;
+    using System.Text;
+    using System.Threading.Tasks;
     ```
 
 2. Add constants to the `Program` class for the Event Hubs connection string and entity path (individual event hub name). Replace the placeholders in brackets with the proper values that were obtained when creating the event hub. Make sure that the `{Event Hubs connection string}` is the namespace-level connection string, and not the event hub string.