Merge pull request #215583 from MicrosoftDocs/main

Publish to live, Monday 4 AM PST, 10/24

Author: ttorble

articles/active-directory-b2c/threat-management.md

@@ -55,7 +55,7 @@ The smart lockout feature uses many factors to determine when an account should
 - Passwords such as 12456! and 1234567! (or newAccount1234 and newaccount1234) are so similar that the algorithm interprets them as human error and counts them as a single try.
 - Larger variations in pattern, such as 12456! and ABCD2!, are counted as separate tries.
 
-When testing the smart lockout feature, use a distinctive pattern for each password you enter. Consider using password generation web apps, such as `https://password-generator.net/`.
+When testing the smart lockout feature, use a distinctive pattern for each password you enter. Consider using password generation web apps, such as `https://password-gen.com/`.
 
 When the smart lockout threshold is reached, you'll see the following message while the account is locked: **Your account is temporarily locked to prevent unauthorized use. Try again later**. The error messages can be [localized](localization-string-ids.md#sign-up-or-sign-in-error-messages).
 

articles/aks/operator-best-practices-run-at-scale.md

@@ -20,6 +20,7 @@ To scale AKS clusters beyond 1000 nodes, you need to request a node limit quota
 To increase the node limit beyond 1000, you must have the following pre-requisites:
 - An existing AKS cluster that needs the node limit increase. This cluster shouldn't be deleted as that will remove the limit increase.
 - Uptime SLA enabled on your cluster.
+- Clusters should use Kubernetes version 1.23 or above
 
 > [!NOTE] 
 > It may take up to a week to enable your clusters with the larger node limit.

articles/azure-monitor/alerts/alerts-create-new-alert-rule.md

@@ -282,6 +282,7 @@ You can create a new alert rule using the [Azure CLI](/cli/azure/get-started-wit
     ### [Log alert](#tab/log)
 
     To create a log alert rule that monitors count of system event errors:
+
     ```azurecli
     az monitor scheduled-query create -g {ResourceGroup} -n {nameofthealert} --scopes {vm_id} --condition "count \'union Event, Syslog | where TimeGenerated > a(1h) | where EventLevelName == \"Error\" or SeverityLevel== \"err\"\' > 2" --description {descriptionofthealert}
     ```
@@ -299,10 +300,10 @@ You can create a new alert rule using the [Azure CLI](/cli/azure/get-started-wit
      - [az monitor activity-log alert action-group](/cli/azure/monitor/activity-log/alert/action-group): Add an action group to the activity log alert rule.
 
     ---
-
 ## Create a new alert rule using PowerShell
 
 - To create a metric alert rule using PowerShell, use this cmdlet: [Add-AzMetricAlertRuleV2](/powershell/module/az.monitor/add-azmetricalertrulev2)
+- To create a log alert rule using PowerShell, use this cmdlet: [New-AzScheduledQueryRule](/powershell/module/az.monitor/new-azscheduledqueryrule)
 - To create an  activity log alert rule using PowerShell, use this cmdlet: [Set-AzActivityLogAlert](/powershell/module/az.monitor/set-azactivitylogalert)
 
 ## Create an activity log alert rule from the Activity log pane
@@ -450,7 +451,7 @@ The *sampleActivityLogAlert.parameters.json* file contains the values provided f
 
 ## Changes to log alert rule creation experience
 
-If you're creating a new log alert rule, please note that current alert rule wizard is a little different from the earlier experience:
+If you're creating a new log alert rule, note that current alert rule wizard is a little different from the earlier experience:
 
 - Previously, search results were included in the payload of the triggered alert and its associated notifications. The email included only 10 rows from the unfiltered results while the webhook payload contained 1000 unfiltered results. To get detailed context information about the alert so that you can decide on the appropriate action:
     - We recommend using [Dimensions](alerts-types.md#narrow-the-target-using-dimensions). Dimensions provide the column value that fired the alert, giving you context for why the alert fired and how to fix the issue.

articles/azure-monitor/alerts/alerts-manage-alert-rules.md

@@ -49,45 +49,20 @@ To enable recommended alert rules:
 
 ## Manage metric alert rules with the Azure CLI
 
-This section describes how to do manage metric alert rules using the cross-platform [Azure CLI](/cli/azure/get-started-with-azure-cli). The following examples use [Azure Cloud Shell](../../cloud-shell/overview.md). 
+This section describes how to manage metric alert rules using the cross-platform [Azure CLI](/cli/azure/get-started-with-azure-cli). The following examples use [Azure Cloud Shell](../../cloud-shell/overview.md). 
 
 1. In the [portal](https://portal.azure.com/), select **Cloud Shell**.
-
-You can use commands with ``--help`` option to learn more about the command and how to use it. For example, the following command shows you the list of commands available for creating, viewing, and managing metric alerts.
-
-```azurecli
-az monitor metrics alert --help
-```
-
-### View all the metric alerts in a resource group
-
-```azurecli
-az monitor metrics alert list  -g {ResourceGroup}
-```
-
-### See the details of a particular metric alert rule
-
-Use the name or the resource ID of the rule in the following commands:
-
-```azurecli
-az monitor metrics alert show -g {ResourceGroup} -n {AlertRuleName}
-```
-
-```azurecli
-az monitor metrics alert show --ids {RuleResourceId}
-```
-
-### Disable a metric alert rule
-
-```azurecli
-az monitor metrics alert update -g {ResourceGroup} -n {AlertRuleName} --enabled false
-```
-
-### Delete a metric alert rule
-
-```azurecli
-az monitor metrics alert delete -g {ResourceGroup} -n {AlertRuleName}
-```
+1. Use these options of the `az monitor metrics alert` CLI command in this table:
+
+    
+    |What you want to do|CLI command  |
+    |---------|---------|
+    |View all the metric alerts in a resource group|`az monitor metrics alert list -g {ResourceGroup}`|
+    |See the details of a metric alert rule|`az monitor metrics alert show -g {ResourceGroup} -n {AlertRuleName}`|
+    |     |`az monitor metrics alert show --ids {RuleResourceId}`|
+    |Disable a metric alert rule|`az monitor metrics alert update -g {ResourceGroup} -n {AlertRuleName} --enabled false`|
+    |Delete a metric alert rule|`az monitor metrics alert delete -g {ResourceGroup} -n {AlertRuleName}`|
+    |Learn more about the command|`az monitor metrics alert --help`|
 
 ## Manage metric alert rules with PowerShell
 
@@ -115,41 +90,17 @@ This section describes how to manage log alerts using the cross-platform [Azure
 
 
 1. In the [portal](https://portal.azure.com/), select **Cloud Shell**.
-
-You can use commands with ``--help`` option to learn more about the command and how to use it. For example, the following command shows you the list of commands available for creating, viewing, and managing log alerts.
-
-```azurecli
-az monitor scheduled-query --help
-```
-
-### View all the log alert rules in a resource group
-
-```azurecli
-az monitor scheduled-query list -g {ResourceGroup}
-```
-
-### See the details of a log alert rule
-
-Use the name or the resource ID of the rule in the following command:
-
-```azurecli
-az monitor scheduled-query show -g {ResourceGroup} -n {AlertRuleName}
-```
-```azurecli
-az monitor scheduled-query show --ids {RuleResourceId}
-```
-
-### Disable a log alert rule
-
-```azurecli
-az monitor scheduled-query update -g {ResourceGroup} -n {AlertRuleName} --disabled true
-```
-
-### Delete a log alert rule
-
-```azurecli
-az monitor scheduled-query delete -g {ResourceGroup} -n {AlertRuleName}
-```
+1. Use these options of the `az monitor scheduled-query alert` CLI command in this table:
+
+    
+    |What you want to do|CLI command  |
+    |---------|---------|
+    |View all the log alert rules in a resource group|`az monitor scheduled-query list -g {ResourceGroup}`|
+    |See the details of a log alert rule|`az monitor scheduled-query show -g {ResourceGroup} -n {AlertRuleName}`|
+    |     |`az monitor scheduled-query show --ids {RuleResourceId}`|
+    |Disable a log alert rule|`az monitor scheduled-query update -g {ResourceGroup} -n {AlertRuleName} --disabled true`|
+    |Delete a log alert rule|`az monitor scheduled-query delete -g {ResourceGroup} -n {AlertRuleName}`|
+    |Learn more about the command|`az monitor scheduled-query --help`|
 
 ### Manage log alert rules using the Azure Resource Manager CLI with [templates](./alerts-log-create-templates.md)
 
@@ -164,6 +115,10 @@ az deployment group create \
 
 A 201 response is returned on successful creation. 200 is returned on successful updates.
 
+## Manage log alert rules with PowerShell
+
+Log alert rules have this dedicated PowerShell cmdlet:
+- [New-AzScheduledQueryRule](/powershell/module/az.monitor/new-azscheduledqueryrule): Creates a new log alert rule or updates an existing log alert rule.
 ## Manage activity log alert rules using PowerShell
 
 Activity log alerts have these dedicated PowerShell cmdlets:

articles/data-factory/TOC.yml

@@ -1180,7 +1180,7 @@ items:
       - name: Azure files
         href: connector-troubleshoot-azure-files.md
         displayName: troubleshooting
-      - name: Azure Synapse Analytics, Azure SQL Database, and SQL Server
+      - name: Azure Synapse Analytics, Azure SQL Database, SQL Server, Azure SQL Managed Instance, and Amazon RDS for SQL Server
         href: connector-troubleshoot-synapse-sql.md
         displayName: troubleshooting
       - name: Azure Table Storage

articles/data-factory/azure-ssis-integration-runtime-express-virtual-network-injection.md

@@ -74,7 +74,7 @@ For more information, see the [DNS server name resolution](../virtual-network/vi
 
 At present, for Azure-SSIS IR to use your own DNS server, you need to configure it with a standard custom setup following these steps:
 
-1. Download a custom setup script ([main.cmd](https://expressvnet.blob.core.windows.net/customsetup/main.cmd)) + its associated file ([setupdnsserver.ps1](https://expressvnet.blob.core.windows.net/customsetup/setupdnsserver.ps1)).
+1. Download a custom setup script ([main.cmd](https://expressvnet.blob.core.windows.net/customsetup/main.cmd?sp=r&st=2022-10-24T07:34:04Z&se=2042-10-24T15:34:04Z&spr=https&sv=2021-06-08&sr=b&sig=dfU16IBua6T%2FB2splQS6rZIXmgkSABaFUZd6%2BWF7fnc%3D)) + its associated file ([setupdnsserver.ps1](https://expressvnet.blob.core.windows.net/customsetup/setupdnsserver.ps1?sp=r&st=2022-10-24T07:36:00Z&se=2042-10-24T15:36:00Z&spr=https&sv=2021-06-08&sr=b&sig=TbspnXbFQv3NPnsRkNe7Q84EdLQT2f1KL%2FxqczFtaw0%3D)).
 
 1. Replace “your-dns-server-ip” in main.cmd with the IP address of your own DNS server.
 

articles/data-factory/connector-office-365.md

@@ -28,6 +28,7 @@ This Microsoft 365 (Office 365) connector is supported for the following capabil
 |---------| --------|
 |[Copy activity](copy-activity-overview.md) (source/-)|① ②|
 |[Mapping data flow](concepts-data-flow-overview.md) (source/-)|①|
+|[Lookup activity](control-flow-lookup-activity.md) (source/-)|① ②|
 
 <small>*&#9312; Azure integration runtime &#9313; Self-hosted integration runtime*</small>
 
@@ -176,6 +177,7 @@ If you were setting `dateFilterColumn`, `startTime`, `endTime`, and `userScopeFi
 
 For a full list of sections and properties available for defining activities, see the [Pipelines](concepts-pipelines-activities.md) article. This section provides a list of properties supported by Microsoft 365 (Office 365) source.
 
+
 ### Microsoft 365 (Office 365) as source
 
 To copy data from Microsoft 365 (Office 365), the following properties are supported in the copy activity **source** section:
@@ -360,5 +362,9 @@ To create a mapping data flow using the Microsoft 365 connector as a source, com
 
 6. On the tab **Data preview** click on the **Refresh** button to fetch a sample dataset for validation.
 
+## Lookup activity properties
+
+To learn details about the properties, check [Lookup activity](control-flow-lookup-activity.md).
+
 ## Next steps
 For a list of data stores supported as sources and sinks by the copy activity, see [supported data stores](copy-activity-overview.md#supported-data-stores-and-formats).

articles/data-factory/connector-troubleshoot-synapse-sql.md

@@ -1,11 +1,11 @@
 ---
-title: Troubleshoot the Azure Synapse Analytics, Azure SQL Database, and SQL Server connectors
+title: Troubleshoot the Azure Synapse Analytics, Azure SQL Database, SQL Server, Azure SQL Managed Instance, and Amazon RDS for SQL Server connectors
 titleSuffix: Azure Data Factory & Azure Synapse
-description: Learn how to troubleshoot issues with the Azure Synapse Analytics, Azure SQL Database, and SQL Server connectors in Azure Data Factory and Azure Synapse Analytics.
+description: Learn how to troubleshoot issues with the Azure Synapse Analytics, Azure SQL Database, SQL Server connectors, Azure SQL Managed Instance, and Amazon RDS for SQL Server in Azure Data Factory and Azure Synapse Analytics.
 author: jianleishen
 ms.author: jianleishen
 ms.reviewer: joanpo, wiassaf
-ms.date: 09/20/2022
+ms.date: 10/18/2022
 ms.service: data-factory
 ms.subservice: data-movement
 ms.topic: troubleshooting
@@ -14,11 +14,11 @@ ms.custom:
   - synapse
 ---
 
-# Troubleshoot the Azure Synapse Analytics, Azure SQL Database, and SQL Server connectors in Azure Data Factory and Azure Synapse
+# Troubleshoot the Azure Synapse Analytics, Azure SQL Database, SQL Server, Azure SQL Managed Instance, and Amazon RDS for SQL Server connectors in Azure Data Factory and Azure Synapse
 
 [!INCLUDE[appliesto-adf-asa-md](includes/appliesto-adf-asa-md.md)]
 
-This article provides suggestions to troubleshoot common problems with the Azure Synapse Analytics, Azure SQL Database, and SQL Server connectors in Azure Data Factory and Azure Synapse.
+This article provides suggestions to troubleshoot common problems with the Azure Synapse Analytics, Azure SQL Database, SQL Server, Azure SQL Managed Instance, and Amazon RDS for SQL Server connectors in Azure Data Factory and Azure Synapse.
 
 ## Error code: SqlFailedToConnect
 
@@ -33,7 +33,8 @@ This article provides suggestions to troubleshoot common problems with the Azure
     | If the error message contains the string "SqlException", SQL Database the error indicates that some specific operation failed. | For more information, search by SQL error code in [Database engine errors](/sql/relational-databases/errors-events/database-engine-events-and-errors). For further help, contact Azure SQL support. |
     | If this is a transient issue (for example, an instable network connection), add retry in the activity policy to mitigate. | For more information, see [Pipelines and activities](./concepts-pipelines-activities.md#activity-policy). |
     | If the error message contains the string "Client with IP address '...' is not allowed to access the server", and you're trying to connect to Azure SQL Database, the error is usually caused by an Azure SQL Database firewall issue. | In the Azure SQL Server firewall configuration, enable the **Allow Azure services and resources to access this server** option. For more information, see [Azure SQL Database and Azure Synapse IP firewall rules](/azure/azure-sql/database/firewall-configure). |
-
+    |If the error message contains `Login failed for user '<token-identified principal>'`, this error is usually caused by not granting enough permission to your service principal or system-assigned managed identity or user-assigned managed identity (depends on which authentication type you choose) in your database. |Grant enough permission to your service principal or system-assigned managed identity or user-assigned managed identity in your database.  <br/><br/> **For Azure SQL Database**:<br/>&nbsp;&nbsp;&nbsp;&nbsp;- If you use service principal authentication, follow [Service principal authentication](connector-azure-sql-database.md#service-principal-authentication).<br/>&nbsp;&nbsp;&nbsp;&nbsp;- If you use system-assigned managed identity authentication, follow [System-assigned managed identity authentication](connector-azure-sql-database.md#managed-identity).<br/>&nbsp;&nbsp;&nbsp;&nbsp;- If you use user-assigned managed identity authentication, follow [User-assigned managed identity authentication](connector-azure-sql-database.md#user-assigned-managed-identity-authentication). <br/>&nbsp;&nbsp;&nbsp;<br/>**For Azure Synapse Analytics**:<br/>&nbsp;&nbsp;&nbsp;&nbsp;- If you use service principal authentication, follow [Service principal authentication](connector-azure-sql-data-warehouse.md#service-principal-authentication).<br/>&nbsp;&nbsp;&nbsp;&nbsp;- If you use system-assigned managed identity authentication, follow [System-assigned managed identities for Azure resources authentication](connector-azure-sql-data-warehouse.md#managed-identity).<br/>&nbsp;&nbsp;&nbsp;&nbsp;- If you use user-assigned managed identity authentication, follow [User-assigned managed identity authentication](connector-azure-sql-data-warehouse.md#user-assigned-managed-identity-authentication).<br/>&nbsp;&nbsp;&nbsp;<br/>**For Azure SQL Managed Instance**: <br/>&nbsp;&nbsp;&nbsp;&nbsp;- If you use service principal authentication, follow [Service principal authentication](connector-azure-sql-managed-instance.md#service-principal-authentication).<br/>&nbsp;&nbsp;&nbsp;- If you use system-assigned managed identity authentication, follow [System-assigned managed identity authentication](connector-azure-sql-managed-instance.md#managed-identity).<br/>&nbsp;&nbsp;&nbsp;- If you use user-assigned managed identity authentication, follow [User-assigned managed identity authentication](connector-azure-sql-managed-instance.md#user-assigned-managed-identity-authentication).|
+    
 ## Error code: SqlOperationFailed
 
 - **Message**: `A database operation failed. Please search error to get more details.`