-| | Streaming - Default | Streaming - Asynchronous Modified Filter |

-> If the virtual network Application Gateway is deployed into doesn't reside in the same resource group as the AKS nodes, please ensure the identity used by AGIC has the **Microsoft.Network/virtualNetworks/subnets/join/action** permission delegated to the subnet Application Gateway is deployed into. If a custom role is not defined with this permission, you may use the built-in **Network Contributor** role, which contains the **Microsoft.Network/virtualNetworks/subnets/join/action** permission.

-If the virtual network Application Gateway is deployed into doesn't reside in the same resource group as the AKS nodes, please ensure the identity used by AGIC has the **Microsoft.Network/virtualNetworks/subnets/join/action** permission delegated to the subnet Application Gateway is deployed into. If a custom role is not defined with this permission, you may use the built-in _Network Contributor_ role, which contains the _Microsoft.Network/virtualNetworks/subnets/join/action_ permission.

-| [PowerShell](#powershell-runbooks) |Textual runbook based on Windows PowerShell scripting. The currently supported versions are: PowerShell 7.2 (GA) and PowerShell 5.1 (GA). Since [PowerShell 7.1](https://learn.microsoft.com/powershell/scripting/install/powershell-support-lifecycle?view=powershell-7.3#powershell-end-of-support-dates) is no longer supported by parent product PowerShell, we recommend you to create runbooks in long term supported version PowerShell 7.2 |

-* Runbooks taking dependency on internal file paths such as `C:\modules` might fail due to changes in service backend infrastructure. Change runbook code to ensure there are no dependencies on internal file paths and use [Get-ChildItem](/powershell/module/microsoft.powershell.management/get-childitem?view=powershell-7.3) to get the required module information.

-> The View/Delete calls for runbook remains same and can be referenced [Runbook - REST API Azure Automation | Microsoft Learn](https://learn.microsoft.com/rest/api/automation/runbook?view=rest-automation-2019-06-01).

-> Create/View calls for job remains same and can be referenced from [Job-REST API (Azure Automation) | Microsoft Learn](https://learn.microsoft.com/rest/api/automation/job?view=rest-automation-2019-06-01).

-> [PowerShell 7.1](https://learn.microsoft.com/powershell/scripting/install/powershell-support-lifecycle?view=powershell-7.3#powershell-end-of-support-dates) and [Python 2.7](https://devguide.python.org/versions/) are no longer supported by their respective parent products PowerShell and Python. We recommend that you update outdated runbooks to latest supported versions using Runtime environment.

-To upgrade a resource bridge on Azure Stack HCI, please transition to 23H2 and use the built-in upgrade management tool. More info available [here](/azure-stack/hci/update/whats-the-lifecycle-manager-23h2).

- > * The query contains the **search**, **union** or **take** (limit) operations

-Stateful log alerts have limitations - details [here](https://learn.microsoft.com/azure/azure-monitor/service-limits#alerts).

-When you create a log alert rule with system-assigned managed identity, the identity is created without any permissions. After you create the rule, you need to assign the appropriate roles to the ruleΓÇÖs identity so that it can access the data you want to query. For example, you might need to give it a Reader role for the relevant Log Analytics workspaces, or a Reader role and a Database Viewer role for the relevant ADX cluster. See [managed identities](https://learn.microsoft.com/azure/azure-monitor/alerts/alerts-create-log-alert-rule#configure-the-alert-rule-details) for more information about using managed identities in log alerts.

- | **Client Id** | Enter the client ID that you want to use for OAuth2 authentication, which you generated earlier. For more information on generating a client ID and a secret, see [Set up OAuth](https://learn.microsoft.com/azure/azure-monitor/alerts/itsmc-connections-servicenow#oauth-setup). |

-For more details, visit [Azure CLI for Azure Monitor Workspace](https://learn.microsoft.com/cli/azure/monitor/account?view=azure-cli-latest)

-For more details, visit [Azure CLI for Azure Monitor Workspace](https://learn.microsoft.com/cli/azure/monitor/account?view=azure-cli-latest)

- "capacity": 500

- "capacity": 500

- "minCapacity": 500

-

-For using VMware Cloud Director Availability outside of the local network segment, [turn on public IP addresses to an NSX-T Edge node for NSX-T Data Center](https://learn.microsoft.com/azure/azure-vmware/enable-public-ip-nsx-edge).

-For more information, go to [Run Command in Azure VMware Solution](https://learn.microsoft.com/azure/azure-vmware/concepts-run-command).

-In this article, you learn how to implement the reactions capability with Azure Communication Services Calling SDKs. This capability allows users in a group call or meeting to send and receive reactions with participants in Azure Communication Services and Microsoft Teams. Reactions for users in Microsoft Teams are controlled by the configuration and policy settings in Teams. Additional information is available in [Manage reactions in Teams meetings and webinars](/microsoftteams/manage-reactions-meetings) and [Meeting options in Microsoft Teams](https://support.microsoft.com/en-us/office/meeting-options-in-microsoft-teams-53261366-dbd5-45f9-aae9-a70e6354f88e)

-To hide this bot from participant roster we need to add specific metadata information, it will be used by Azure Communication SDK and Teams client:

-```json

- "metadata": {"__platform":{"ui":{"hidden":true}

-```

- 2) Follow this [article](https://learn.microsoft.com/sql/relational-databases/collations/set-or-change-the-column-collation?) to manually change collation.

- 1. Install Pre requisites Az PowerShell modules (https://learn.microsoft.com/powershell/azure/install-az-ps)

-Single-tenant Azure Logic Apps gives you the option to select your preferred compute resources and set up your logic app resources to dynamically scale based on varying workload demands. The target-based scaling model used by Azure Logic Apps includes settings that you can use to fine-tune the model's underlying dynamic scaling mechanism, which can result in faster scale-out and scale-in times. For more information about the target-based scaling model, see the following articles:

-> Perform this step only if you are migrating to [Azure Stack HCI](https://learn.microsoft.com/azure-stack/hci/overview).

-Provide the Azure Stack cluster information and the credentials to connect to the cluster. For more information, see [Download the Azure Stack HCI software](https://learn.microsoft.com/azure-stack/hci/deploy/download-azure-stack-hci-software).

-## Create a private endpoint using PowerShell

-The following example shows how to use PowerShell to create a private endpoint connection to a Notification Hubs namespace. Your private endpoint uses a private IP address in your virtual network.

-1. Sign in to Azure via PowerShell and set a subscription:

- ```powershell

- Login-AzAccount

- Set-AzContext -SubscriptionId <azure_subscription_id>

- ```

-1. Create a new resource group:

- ```powershell

- New-AzResourceGroup -Name <resource_group_name> -Location <azure_region>

- ```

-1. Register **Microsoft.NotificationHubs** as a resource provider:

- ```powershell

- Register-AzResourceProvider -ProviderNamespace Microsoft.NotificationHubs

- ```

-1. Create a new Azure Notification Hubs namespace:

- ```powershell

- New-AzNotificationHubsNamespace -ResourceGroup <resource_group_name> -Location <azure_region> -Namespace <namespace_name> -SkuTier "Standard"

- ```

-1. Create a new notification hub. First, create a JSON file with the notification hub details. This file is used as an input to the create notification hub PowerShell command. Paste the following content into the JSON file:

- ```json

- {

- "ResourceGroup": "resource_group_name",

- "NamespaceName": "namespace_name",

- "Location": "azure_region",

- "Name": "notification_hub_name"

- }

- ```

-1. Run the following PowerShell command:

- ```powershell

- New-AzNotificationHub -ResourceGroup <resource_group_name> -Namespace <namespace_name> -InputFile <path_to_json_file>

- ```

-1. Create a virtual network with a subnet:

- ```powershell

- New-AzVirtualNetwork -ResourceGroup <resource_group_name> -Location <azure_region> -Name <your_VNet_name> -AddressPrefix <address_prefix>

- Add-AzVirtualNetworkSubnetConfig -VirtualNetwork (Get-AzVirtualNetwork -Name <your_VNet_name> -ResourceGroup <resource_group_name>) -Name <subnet_name> -AddressPrefix <address_prefix>

- ```

-1. Disable virtual network policies:

- ```powershell

- $net = @{

- Name = 'myVNet'

- ResourceGroupName = 'RG'

- }

- $vnet = Get-AzVirtualNetwork @net

- $sub = @{

- Name = <subnet_name>

- VirtualNetwork = $vnet

- PrivateEndpointNetworkPoliciesFlag = 'Disabled'

- }

- Set-AzVirtualNetworkSubnetConfig @sub

- ```

-1. Add private DNS zones and link them to the virtual network:

- ```powershell

- New-AzPrivateDnsZone -ResourceGroup <resource_group_name> -Name privatelink.servicebus.windows.net

- New-AzPrivateDnsZone -ResourceGroup <resource_group_name> -Name privatelink.notificationhub.windows.net

-

- New-AzPrivateDnsVirtualNetworkLink -ResourceGroup <resource_group_name> -Name <dns_Zone_Link_Name> -ZoneName "privatelink.servicebus.windows.net" -VirtualNetworkId "/subscriptions/<azure_subscription_id>/resourceGroups/<resource_group_name>/providers/Microsoft.Network/virtualNetworks/<vNet_name>"

-

- New-AzPrivateDnsVirtualNetworkLink -ResourceGroup <resource_group_name> -Name <dns_Zone_Link_Name> -ZoneName "privatelink.notificationhub.windows.net" -VirtualNetworkId "/subscriptions/<azure_subscription_id>/resourceGroups/<resource_group_name>/providers/Microsoft.Network/virtualNetworks/<vNet_name>"

- ```

-1. Create a private endpoint:

- ```powershell

- $plsConnection= New-AzPrivateLinkServiceConnection -Name <private_link_connection_name> -PrivateLinkServiceId '/subscriptions/<azure_subscription_id> /resourceGroups/<resource_group_name>/providers/Microsoft.NotificationHubs/namespaces/<namespace_name>'

-

- New-AzPrivateEndpoint -ResourceGroup <resource_group_name> -Location <azure_region> -Name <private_endpoint_name> -Subnet (Get-AzVirtualNetworkSubnetConfig -Name <subnet_name> -VirtualNetwork (Get-AzVirtualNetwork -Name <vNet_name> -ResourceGroup <resource_group_name>)) -PrivateLinkServiceConnection $plsConnection

- ```

-1. Show the connection status:

- ```powershell

- Get-AzPrivateEndpointConnection -ResourceGroup <resource_group_name> -Name <private_endpoint_name>

- ```

-You can create the extension by running:

-SELECT create_extension('azure_storage');

-Your Azure blob storage (ABS) access keys are similar to a root password for your storage account. Always be careful to protect your access keys. Use Azure Key Vault to manage and rotate your keys securely. The account key is stored in a table that is accessible by the postgres superuser, azure_storage_admin and all roles granted those admin permissions. To see which storage accounts exist, use the function account_list.

-When was the file content last modified?

-#### content_encode

-This hash is used to verify the integrity of the blob during transport. When this header is specified, the storage service checks the hash that has arrived with the one that was sent. If the two hashes don't match, the operation fails with error code 400 (Bad Request).

-SETOF Record / any element

-Specifies the character that separates columns within each row (line) of the file. The default is a tab character in text format, a comma in CSV format. It must be a single one-byte character.

-#### null_str

-Specifies that the file contains a header line with the names of each column in the file. On output, the frontline contains the column names from the table.

-Specifies the quoting character to be used when a data value is quoted. The default is double-quote. It must be a single one-byte character.

-Specifies the character that should appear before a data character that matches the QUOTE value. The default is the same as the QUOTE value (so that the quoting character is doubled if it appears in the data). It must be a single one-byte character.

-Match the specified columns' values against the null string, even if it has been quoted, and if a match is found set the value to NULL. In the default case where the null string is empty, it converts a quoted empty string into NULL.

-#### content_encode

-Specifies the character that separates columns within each row (line) of the file. The default is a tab character in text format, a comma in CSV format. It must be a single one-byte character.

-#### null_str

-Specifies that the file contains a header line with the names of each column in the file. On output, the frontline contains the column names from the table.

-Specifies the quoting character to be used when a data value is quoted. The default is double-quote. It must be a single one-byte character.

-Specifies the character that should appear before a data character that matches the QUOTE value. The default is the same as the QUOTE value (so that the quoting character is doubled if it appears in the data). It must be a single one-byte character.

-Match the specified columns' values against the null string, even if it has been quoted, and if a match is found set the value to NULL. In the default case where the null string is empty, it converts a quoted empty string into NULL.

-#### content_encode

-Specifies the character that separates columns within each row (line) of the file. The default is a tab character in text format, a comma in CSV format. It must be a single one-byte character.

-#### null_str

-#### content_encode

-#### content_encode

-> [!NOTE]

-**Permissions**

-Now you can list containers set to Private and Blob access levels for that storage but only as the `citus user`, which has the `azure_storage_admin` role granted to it. If you create a new user named support, it won't be allowed to access container contents by default.

-> Ensure that any actions taken are performed from a trusted device, built from a clean source. For example, use a fresh, privileged access workstation.

-|**Reset passwords to privileged accounts** | Reset passwords of all privileged accounts in the environment. <br><br>**Note**: Privileged accounts are not limited to built-in groups, but can also be groups that are delegated access to server administration, workstation administration, or other areas of your environment. |

-2. Use the [`Replication Protected Items - Update`](https://learn.microsoft.com/rest/api/site-recovery/replication-protected-items/update?view=rest-site-recovery-2023-02-01&tabs=HTTP&tryIt=true&source=docs#diskencryptioninfo) Rest API to update the Azure Site Recovery metadata.

-1. Use the [`Set-AzRecoveryServicesAsrReplicationProtectedItem`](https://learn.microsoft.com/powershell/module/az.recoveryservices/set-azrecoveryservicesasrreplicationprotecteditem?view=azps-11.1.0) command to update the Azure Site Recovery metadata.

- Periodic assessment is an update setting on a machine that allows you to enable automatic periodic checking of updates by Update Manager. We recommend that you enable this property on your machines as it allows Update Manager to fetch latest updates for your machines every 24 hours and enables you to view the latest compliance status of your machines. You can enable this setting using update settings flow as detailed [here](manage-update-settings.md#configure-settings-on-a-single-vm) or enable it at scale by using [Policy](periodic-assessment-at-scale.md).

- > [!NOTE]

- > You can associate one dynamic scope to one schedule.

- Learn about deploying updates to your machines to maintain security compliance by reading [deploy updates](deploy-updates.md)

-2 | Enable periodic assessment to check for latest updates automatically every few hours. | Machines automatically receive the latest updates every 12 hours for Windows and every 3 hours for Linux. | Periodic assessment is an update setting on your machine. If it's turned on, the Update Manager fetches updates every 24 hours for the machine and shows the latest update status. | 1. [Single machine](manage-update-settings.md#configure-settings-on-a-single-vm) </br> 2. [At scale](manage-update-settings.md#configure-settings-at-scale) </br> 3. [At scale using policy](periodic-assessment-at-scale.md) | 1. [For Azure VM](../virtual-machines/automatic-vm-guest-patching.md#azure-powershell-when-updating-a-windows-vm) </br> 2.[For Arc-enabled VM](/powershell/module/az.connectedmachine/update-azconnectedmachine?view=azps-10.2.0) |

-> [!NOTE]

-> The schedules associated to dynamic scopes arenΓÇÖt displayed in the following two areas by design:

->

-> - **Update manager** > **Machines** > **Associated schedules** column

-> - In your virtual machine home page > **Updates** > **Scheduling** tab.

->

-> To view the VMs that are associated to the schedule, go to the existing schedule and view under **Dynamic scopes** tab.

-* [View updates for single machine](view-updates.md)

-* [Deploy updates now (on-demand) for single machine](deploy-updates.md)

-* [Schedule recurring updates](scheduled-patching.md)

-* [Manage update settings via Portal](manage-update-settings.md)

-* [Manage multiple machines using update Manager](manage-multiple-machines.md)

-To troubleshoot issues, see [Troubleshoot Update Manager](troubleshoot.md).

-* To view update assessment and deployment logs generated by Update Manager, see [Query logs](query-logs.md).

-* To troubleshoot issues, see [Troubleshoot Update Manager](troubleshoot.md).