| Service | Microsoft Docs article | Related commit history on GitHub | Change details |
|---|---|---|---|
| active-directory | Whats New Docs | https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/develop/whats-new-docs.md | +## June 2022 ++### Updated articles ++- [Add app roles to your application and receive them in the token](howto-add-app-roles-in-azure-ad-apps.md) +- [Azure AD Authentication and authorization error codes](reference-aadsts-error-codes.md) +- [Microsoft identity platform refresh tokens](refresh-tokens.md) +- [Single-page application: Acquire a token to call an API](scenario-spa-acquire-token.md) +- [Tutorial: Sign in users and call the Microsoft Graph API in an Electron desktop app](tutorial-v2-nodejs-desktop.md) + ## May 2022 ### Updated articles Welcome to what's new in the Microsoft identity platform documentation. This art - [Quickstart: Sign in users and call the Microsoft Graph API from an Android app](mobile-app-quickstart-portal-android.md) - [Quickstart: Sign in users and call the Microsoft Graph API from an iOS or macOS app](mobile-app-quickstart-portal-ios.md) - [Set up your application's Azure AD test environment](test-setup-environment.md)-- [Single Sign-On SAML protocol](single-sign-on-saml-protocol.md)+- [Single sign-on SAML protocol](single-sign-on-saml-protocol.md) - [Single sign-on with MSAL.js](msal-js-sso.md) - [Tutorial: Sign in users and acquire a token for Microsoft Graph in a Node.js & Express web app](tutorial-v2-nodejs-webapp-msal.md) - [What's new for authentication?](reference-breaking-changes.md) Welcome to what's new in the Microsoft identity platform documentation. This art - [OAuth 2.0 and OpenID Connect in the Microsoft identity platform](active-directory-v2-protocols.md) - [Signing key rollover in the Microsoft identity platform](active-directory-signing-key-rollover.md) - [Troubleshoot publisher verification](troubleshoot-publisher-verification.md)--## February 2022 --### Updated articles --- [Desktop app that calls web APIs: Acquire a token using WAM](scenario-desktop-acquire-token-wam.md) |
| active-directory | Whats New Docs | https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/manage-apps/whats-new-docs.md | Title: "What's new in Azure Active Directory application management" description: "New and updated documentation for the Azure Active Directory application management." Previously updated : 06/22/2022 Last updated : 07/04/2022 +## June ++### Updated articles ++- [Protect against consent phishing](protect-against-consent-phishing.md) +- [Request to Publish your application in the Azure Active Directory application gallery](v2-howto-app-gallery-listing.md) + ## May 2022 ### New articles Welcome to what's new in Azure Active Directory application management documenta - [Tutorial: Configure F5ΓÇÖs BIG-IP Easy Button for SSO to Oracle JDE](f5-big-ip-oracle-jde-easy-button.md) - [Tutorial: Configure F5ΓÇÖs BIG-IP Easy Button for SSO to Oracle PeopleSoft](f5-big-ip-oracle-peoplesoft-easy-button.md) - [Tutorial: Manage certificates for federated single sign-on](tutorial-manage-certificates-for-federated-single-sign-on.md)--## February 2022 --### New articles --- [Properties of an enterprise application](application-properties.md)-- [Tutorial: Configure F5ΓÇÖs BIG-IP Easy Button for SSO to Oracle PeopleSoft](f5-big-ip-oracle-peoplesoft-easy-button.md)-- [Tutorial: Govern and monitor applications](tutorial-govern-monitor.md)-- [Tutorial: Manage application access and security](tutorial-manage-access-security.md)--### Updated articles --- [Configure enterprise application properties](add-application-portal-configure.md)-- [Configure F5 BIG-IP Access Policy Manager for form-based SSO](f5-big-ip-forms-advanced.md)-- [Configure sign-in behavior using Home Realm Discovery](configure-authentication-for-federated-users-portal.md)-- [Disable auto-acceleration sign-in](prevent-domain-hints-with-home-realm-discovery.md)-- [Home Realm Discovery for an application](home-realm-discovery-policy.md)-- [Integrate F5 BIG-IP with Azure Active Directory](f5-aad-integration.md)-- [Overview of enterprise application ownership in Azure Active Directory](overview-assign-app-owners.md)-- [Tutorial: Configure F5 BIG-IPΓÇÖs Access Policy Manager for header-based SSO](f5-big-ip-header-advanced.md)-- [Tutorial: Configure F5 BIG-IP Access Policy Manager for Kerberos authentication](f5-big-ip-kerberos-advanced.md)-- [Tutorial: Configure F5ΓÇÖs BIG-IP Easy Button for header-based SSO](f5-big-ip-headers-easy-button.md)-- [Tutorial: Configure F5 BIG-IP Easy Button for header-based and LDAP SSO](f5-big-ip-ldap-header-easybutton.md)-- [Tutorial: Configure F5ΓÇÖs BIG-IP Easy Button for SSO to Oracle JDE](f5-big-ip-oracle-jde-easy-button.md)-- [Tutorial: Configure F5ΓÇÖs BIG-IP Easy Button for SSO to Oracle EBS](f5-big-ip-oracle-enterprise-business-suite-easy-button.md)-- [Tutorial: Configure F5 BIG-IP Easy Button for Kerberos SSO](f5-big-ip-kerberos-easy-button.md)-- [Tutorial: Configure F5 BIG-IP SSL-VPN for Azure AD SSO](f5-aad-password-less-vpn.md)-- [Tutorial: Manage application access and security](tutorial-manage-access-security.md)-- [What is application management in Azure Active Directory?](what-is-application-management.md) |
| azure-web-pubsub | Reference Functions Bindings | https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-web-pubsub/reference-functions-bindings.md | public static object Run( { if (wpsContext.IsPreflight || !wpsContext.HasError) {- return wpsReq.Response; + return wpsContext.Response; }- var request = wpsReq.Request as ConnectEventRequest; + var request = wpsContext.Request as ConnectEventRequest; var response = new ConnectEventResponse { UserId = wpsContext.Request.ConnectionContext.UserId module.exports = async function (context, req, wpsContext) { if (!wpsContext.hasError || wpsContext.isPreflight) { console.log(`invalid request: ${wpsContext.response.message}.`);- return wpsReq.response; + return wpsContext.response; } console.log(`user: ${wpsContext.connectionContext.userId} is connecting.`); return { body: {"userId": wpsContext.connectionContext.userId} }; You can also easily [enable console logging](https://github.com/Azure/azure-sdk- ## Next steps |
| backup | Backup Azure Vms Enhanced Policy | https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/backup/backup-azure-vms-enhanced-policy.md | Title: Back up Azure VMs with Enhanced policy description: Learn how to configure Enhanced policy to back up VMs. Previously updated : 06/08/2022 Last updated : 07/04/2022 Follow these steps: >- We support Enhanced policy configuration through [Recovery Services vault](./backup-azure-arm-vms-prepare.md) and [VM Manage blade](./backup-during-vm-creation.md#start-a-backup-after-creating-the-vm) only. Configuration through Backup center is currently not supported. >- For hourly backups, the last backup of the day is transferred to vault. If backup fails, the first backup of the next day is transferred to vault. >- Enhanced policy is only available to unprotected VMs that are new to Azure Backup. Note that Azure VMs that are protected with existing policy can't be moved to Enhanced policy.->- Back up an Azure VM with disks that has public network access disabled, using Enhanced policy, is not supported. +>- Back up an Azure VM with disks that has public network access disabled is not supported. ## Next steps |
| backup | Use Archive Tier Support | https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/backup/use-archive-tier-support.md | Title: Use Archive tier description: Learn about using Archive tier Support for Azure Backup. Previously updated : 03/21/2022 Last updated : 07/04/2022 zone_pivot_groups: backup-client-portaltier-powershelltier-clitier This article provides the procedure to back up long-term retention points in Arc | Workloads | Operations | | | |-| Azure Virtual Machine | View archived recovery points. <br><br> Move all recommended recovery points to archive.<br><br> Restore for archived recovery points. <br><br> View archive move and restore jobs. | +| Microsoft Azure Virtual Machine | View archived recovery points. <br><br> Move all recommended recovery points to archive.<br><br> Restore for archived recovery points. <br><br> View archive move and restore jobs. | | SQL Server in Azure Virtual Machine <br><br> SAP HANA in Azure Virtual Machines | View archived recovery points. <br><br> Move all archivable recovery points to archive. <br><br> Restore from archived recovery points. <br><br> View archive move and restore jobs. | ## View archived recovery points You can now view all the recovery points that are moved to archive. :::image type="content" source="./media/use-archive-tier-support/view-recovery-points-list-inline.png" alt-text="Screenshot showing the list of recovery points." lightbox="./media/use-archive-tier-support/view-recovery-points-list-expanded.png"::: +## Enable Smart Tiering to Vault-archive using a backup policy (preview) ++You can automatically move all eligible/recommended recovery points to vault-archive by configuring the required settings in the backup policy. ++>[!Note] +>This feature is currently in preview. Enable your subscription to use this feature. ++### Enable a subscription for Smart Tiering (preview) ++To enable a subscription, follow these steps: ++1. In the Azure portal, select the subscription you want to enable. ++1. Select **Preview Features** in the left pane. ++ :::image type="content" source="./media/use-archive-tier-support/select-preview-feature-inline.png" alt-text="Screenshot showing to select the Preview Feature option." lightbox="./media/use-archive-tier-support/select-preview-feature-expanded.png"::: ++1. Select **Smart Tiering for Archive**. ++ :::image type="content" source="./media/use-archive-tier-support/select-smart-tiering-for-archive-inline.png" alt-text="Screenshot showing to select Smart Tiering for Archive option." lightbox="./media/use-archive-tier-support/select-smart-tiering-for-archive-expanded.png"::: ++1. Select **Register**. ++The subscription gets enabled for Smart Tiering in a few minutes. ++### Enable Smart Tiering for Azure Virtual Machine ++To enable Smart Tiering for Azure VM backup policies, follow these steps: ++1. In the Azure portal, go to Recovery Services vault -> **Manage** -> **Backup policies**. ++1. Select or create a backup policy: ++ - **Existing Backup Policy**: Select the backup policy for which you want to enable Smart Tiering. + - **Create a new Policy**: Create a new backup policy. ++1. In **Backup policy**, select **Enable Tiering**. ++ :::image type="content" source="./media/use-archive-tier-support/select-enable-tiering-inline.png" alt-text="Screenshot showing to select the Enable Tiering option." lightbox="./media/use-archive-tier-support/select-enable-tiering-expanded.png"::: ++1. Select one of the following options to move to Vault-archive tier: ++ - **Recommended recovery points**: This option moves all recommended recovery points to the vault-archive tier. [Learn more](archive-tier-support.md#archive-recommendations-only-for-azure-virtual-machines) about recommendations. + - **Eligible recovery points**: This option moves all eligible recovery point after a specific number of days. ++ :::image type="content" source="./media/use-archive-tier-support/select-eligible-recovery-points-inline.png" alt-text="Screenshot showing to select the Eligible recovery points option." lightbox="./media/use-archive-tier-support/select-eligible-recovery-points-expanded.png"::: ++ >[!Note] + >- The value of *x* can range from *3 months* to *(monthly/yearly retention in months -6)*. + >- This can increase your overall costs. ++Once the policy is configured, all the recommended recovery points are moved to archive tier. ++### Enable Smart Tiering for SAP HANA/ SQL Servers in Azure Virtual Machines ++To enable Smart Tiering for Azure SAP HANA/SQL servers in Azure VM backup policies, follow these steps: ++1. In the Azure portal, go to Recovery Services vault -> **Manage** -> **Backup policies**. ++1. Select or create a backup policy: ++ - **Existing Backup Policy**: Select the backup policy for which you want to enable smart Tiering. + - **Create a new Policy**: Create a new backup policy. ++1. In **Backup policy**, select **Move eligible recovery points to Vault-archive**. ++ :::image type="content" source="./media/use-archive-tier-support/select-move-eligible-recovery-points-to-vault-archive-inline.png" alt-text="Screenshot showing to select the Move eligible recovery points to Vault-archive option." lightbox="./media/use-archive-tier-support/select-move-eligible-recovery-points-to-vault-archive-expanded.png"::: ++ Select the number of days after which you want to move your recovery point to archive. ++ >[!Note] + >The number of days would range from *45* to *(retention-180)* days. ++Once Smart Tiering is enabled, all the eligible recovery points are moved to the Vault-archive tier. + ## Move archivable recovery points ### Move archivable recovery points for a particular SQL/SAP HANA database Follow these steps: 1. Select **click here** to view the list of all eligible achievable recovery points. - :::image type="content" source="./media/use-archive-tier-support/view-old-recovery-points-inline.png" alt-text="Screenshot showing the process to view recovery points that are older than 7 days." lightbox="./media/use-archive-tier-support/view-old-recovery-points-expanded.png"::: + :::image type="content" source="./media/use-archive-tier-support/view-old-recovery-points-inline.png" alt-text="Screenshot showing the process to view recovery points that are older than seven days." lightbox="./media/use-archive-tier-support/view-old-recovery-points-expanded.png"::: -1. Click **Move recovery points to archive** to move all recovery points to the Vault-archive tier. +1. Select **Move recovery points to archive** to move all recovery points to the Vault-archive tier. :::image type="content" source="./media/use-archive-tier-support/move-all-recovery-points-to-vault-inline.png" alt-text="Screenshot showing the option to start the move process of all recovery points to the Vault-archive tier." lightbox="./media/use-archive-tier-support/move-all-recovery-points-to-vault-expanded.png"::: Follow these steps: 1. Select **click here** to view recommended recovery points. - :::image type="content" source="./media/use-archive-tier-support/view-old-virtual-machine-recovery-points-inline.png" alt-text="Screenshot showing the process to view recovery points for virtual machines that are older than 7 days." lightbox="./media/use-archive-tier-support/view-old-virtual-machine-recovery-points-expanded.png"::: + :::image type="content" source="./media/use-archive-tier-support/view-old-virtual-machine-recovery-points-inline.png" alt-text="Screenshot showing the process to view recovery points for Virtual Machines that are older than seven days." lightbox="./media/use-archive-tier-support/view-old-virtual-machine-recovery-points-expanded.png"::: -1. Click **Move recovery points to archive** to move all the recommended recovery points to Archive tier. +1. Select **Move recovery points to archive** to move all the recommended recovery points to Archive tier. - :::image type="content" source="./media/use-archive-tier-support/move-all-virtual-machine-recovery-points-to-vault-inline.png" alt-text="Screenshot showing the option to start the move process of all recovery points for virtual machines to the Vault-archive tier." lightbox="./media/use-archive-tier-support/move-all-virtual-machine-recovery-points-to-vault-expanded.png"::: + :::image type="content" source="./media/use-archive-tier-support/move-all-virtual-machine-recovery-points-to-vault-inline.png" alt-text="Screenshot showing the option to start the move process of all recovery points for Virtual Machines to the Vault-archive tier." lightbox="./media/use-archive-tier-support/move-all-virtual-machine-recovery-points-to-vault-expanded.png"::: >[!Note] >To ensure cost savings, you need to move all the recommended recovery points to the Vault-archive tier. To verify, follow steps 1 and 2. If the list of recovery points is empty in step 3, all the recommended recovery points are moved to the Vault-archive tier. $rp | select RecoveryPointId, @{ Label="IsArchivable";Expression={$_.RecoveryPoi $rp = Get-AzRecoveryServicesBackupRecoveryPoint -VaultId $vault.ID -Item $bckItm -StartDate $startdate.ToUniversalTime() -EndDate $enddate.ToUniversalTime() -IsReadyForMove $true -TargetTier VaultArchive ``` -This lists all recovery points associated with a particular backup item that are ready to be moved to archive (from the start date to the end date). You can also modify the start dates and the end dates. +This cmdlet lists all recovery points associated with a particular backup item that's ready to be moved to archive (from the start date to the end date). You can also modify the start dates and the end dates. ## Check why a recovery point can't be moved to archive False Recovery-Point Type is not eligible for archive move as it is al ## Check recommended set of archivable points (only for Azure VMs) -The recovery points associated with a virtual machine are incremental. When you move a particular recovery point to archive, it's converted into a full backup, and then moved to archive. So, the cost savings associated with moving to archive depends on the churn of the data source. +The recovery points associated with a Virtual Machine are incremental. When you move a particular recovery point to archive, it's converted into a full backup, then moved to archive. So, the cost savings associated with moving to archive depends on the churn of the data source. Therefore, Azure Backup provides a recommended set of recovery points that might save cost, if moved together. $RecommendedRecoveryPointList = Get-AzRecoveryServicesBackupRecommendedArchivabl Move-AzRecoveryServicesBackupRecoveryPoint -VaultId $vault.ID -RecoveryPoint $rp[0] -SourceTier VaultStandard -DestinationTier VaultArchive ``` -Where, `$rp[0]` is the first recovery point in the list. If you want to move other recovery points, use `$rp[1]`, `$rp[2]`, and so on. +Here, `$rp[0]` is the first recovery point in the list. If you want to move other recovery points, use `$rp[1]`, `$rp[2]`, and so on. This cmdlet moves an archivable recovery point to archive. It returns a job that can be used to track the move operation, both from portal and with PowerShell. For more information about various restore methods for Azure Virtual Machines, s Restore-AzRecoveryServicesBackupItem -VaultLocation $vault.Location -RehydratePriority "Standard" -RehydrateDuration 15 -RecoveryPoint $rp -StorageAccountName "SampleSA" -StorageAccountResourceGroupName "SArgName" -TargetResourceGroupName $vault.ResourceGroupName -VaultId $vault.ID ``` -To restore SQL Server, follow [these steps](backup-azure-sql-automation.md#restore-sql-dbs). The `Restore-AzRecoveryServicesBackupItem` cmdlet requires two additional parameters, `RehydrationDuration` and `RehydrationPriority`. +To restore SQL Server, follow [these steps](backup-azure-sql-automation.md#restore-sql-dbs). The `Restore-AzRecoveryServicesBackupItem` cmdlet requires two other parameters, `RehydrationDuration` and `RehydrationPriority`. ## View jobs This article provides the procedure to back up long-term retention points in the ## Get started -1. Download/Upgrade AZ CLI version to 2.26.0 or higher +1. Download/Upgrade Azure CLI version to 2.26.0 or higher. 1. Follow the [instructions](/cli/azure/install-azure-cli) to install CLI for the first time.- 1. Run az --upgrade to upgrade an already installed version. + 1. Run `az --upgrade` to upgrade an already installed version. -2. Log in using the following command: +2. Sign in using the following command: ```azurecli az login Run the following command: az backup recoverypoint list -g {rg} -v {vault} -c {container} -i {item} --backup-management-type {AzureWorkload / AzureIaasVM} --workload-type {MSSQL / SAPHANA / VM} --query [].{Name:name,move_ready:properties.recoveryPointMoveReadinessInfo.ArchivedRP.isReadyForMove,additional_details: properties.recoveryPointMoveReadinessInfo.ArchivedRP.additionalInfo ``` -You will get a list of all recovery points, whether they are archivable and the reason if they are not archivable +You'll get a list of all recovery points, whether they're archivable and the reason if they're not archivable ## Check recommended set of archivable points (only for Azure VMs) |
| defender-for-cloud | Alert Validation | https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/defender-for-cloud/alert-validation.md | Title: Alert validation in Microsoft Defender for Cloud | Microsoft Docs description: Learn how to validate that your security alerts are correctly configured in Microsoft Defender for Cloud -- Previously updated : 12/12/2021 Last updated : 07/04/2022 # Alert validation in Microsoft Defender for Cloud For more information, see [Security alerts in Defender for Cloud](alerts-overvie ## Generate sample security alerts -If you're using the new, preview alerts experience as described in [Manage and respond to security alerts in Microsoft Defender for Cloud](managing-and-responding-alerts.md), you can create sample alerts in a few clicks from the security alerts page in the Azure portal. +If you're using the new, preview alerts experience as described in [Manage and respond to security alerts in Microsoft Defender for Cloud](managing-and-responding-alerts.md), you can create sample alerts from the security alerts page in the Azure portal. Use sample alerts to: After the Log Analytics agent is installed on your machine, follow these steps f ## Simulate alerts on Kubernetes <a name="validate-kubernetes"></a> -If you've integrated Azure Kubernetes Service with Defender for Cloud, you can test that your alerts are working with the following kubectl command: +Defender for Containers provides security alerts for both your clusters and underlying cluster nodes. Defender for Containers accomplishes this by monitoring both the control plane (API server) and the containerized workload. -`kubectl get pods --namespace=asc-alerttest-662jfi039n` +You can tell if your alert is related to the control plan or the containerized workload based on its prefix. Control plane security alerts have a prefix of `K8S_`, while security alerts for runtime workload in the clusters have a prefix of `K8S.NODE_`. -For more information about defending your Kubernetes nodes and clusters, see [Overview of Microsoft Defender for Containers](defender-for-containers-introduction.md) +You can simulate alerts for both of the control plane, and workload alerts with the following steps. ++### Simulate control plane alerts (K8S_ prefix) ++**Prerequisites** ++- Ensure the Defender for Containers plan is enabled. +- **ARC only** - Ensure the defender extension is installed. +- **EKS or GKE only** - Ensure the default audit log collection auto-provisioning options are enabled. ++**To simulate a Kubernetes control plane security alert**: ++1. Run the following command from the cluster: ++ ```bash + kubectl get pods --namespace=asc-alerttest-662jfi039n + ``` ++ You'll get the following response: `No resource found`. ++1. Wait 30 minutes. ++1. In the Azure portal, navigate to the Defender for Cloud's alerts page. ++1. On the relevant Kubernetes cluster, locate the following alert `Microsoft Defender for Cloud test alert for K8S (not a threat)` ++### Simulate workload alerts (K8S.NODE_ prefix) ++**Prerequisites** ++- Ensure the Defender for Containers plan is enabled. +- Ensure the Defender profile\extension is installed ++**To simulate a a Kubernetes workload security alert**: + +1. Access one of the `azuredefender-publisher-<XXX>` pods deployed in your Kubernetes cluster. ++1. Run the following command from the cluster: ++ ```bash + kubectl exec -it azuredefender-publisher-xx-xxxxx -n <namespace> -- bash + ``` ++ For AKS - `<namespace>` = `kube-system`<br> + For ARC - `<namespace>` = `mdc` ++1. Select an executable, copy it to a convenient location and rename it to `./asc_alerttest_662jfi039n`. For example: +`cp /bin/echo ./asc_alerttest_662jfi039n`. ++1. Execute the file `./asc_alerttest_662jfi039n testing eicar pipe`. ++1. Wait 10 minutes. ++1. In the Azure portal, navigate to the Defender for Cloud's alerts page. ++1. On the relevant AKS cluster, locate the following alert `Microsoft Defender for Cloud test alert (not a threat)`. ++You can also learn more about defending your Kubernetes nodes and clusters with [Microsoft Defender for Containers](defender-for-containers-introduction.md). ## Next steps This article introduced you to the alerts validation process. Now that you're familiar with this validation, try the following articles: -* [Validating Azure Key Vault threat detection in Microsoft Defender for Cloud](https://techcommunity.microsoft.com/t5/azure-security-center/validating-azure-key-vault-threat-detection-in-azure-security/ba-p/1220336) -* [Managing and responding to security alerts in Microsoft Defender for Cloud](managing-and-responding-alerts.md) - Learn how to manage alerts, and respond to security incidents in Defender for Cloud. -* [Understanding security alerts in Microsoft Defender for Cloud](./alerts-overview.md) - Learn about the different types of security alerts. +- [Validating Azure Key Vault threat detection in Microsoft Defender for Cloud](https://techcommunity.microsoft.com/t5/azure-security-center/validating-azure-key-vault-threat-detection-in-azure-security/ba-p/1220336) +- [Managing and responding to security alerts in Microsoft Defender for Cloud](managing-and-responding-alerts.md) - Learn how to manage alerts, and respond to security incidents in Defender for Cloud. +- [Understanding security alerts in Microsoft Defender for Cloud](./alerts-overview.md) |
| sentinel | Ama Migrate | https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/sentinel/ama-migrate.md | Title: Migrate to the Azure Monitor agent (AMA) from the Log Analytics agent (MMA/OMS) for Microsoft Sentinel description: Learn about migrating from the Log Analytics agent (MMA/OMS) to the Azure Monitor agent (AMA), when working with Microsoft Sentinel.-+ Previously updated : 02/09/2022- Last updated : 07/04/2022+ # AMA migration for Microsoft Sentinel The following tables show gap analyses for the log types that currently rely on |**Windows Firewall Logs** | - | [Windows Firewall data connector](data-connectors-reference.md#windows-firewall) | |**Performance counters** | Collection only | Collection only | |**Windows Event Logs** | Collection only | Collection only |-|**Custom logs** | - | Collection only | -|**IIS logs** | - | Collection only | +|**Custom logs** | Collection only | Collection only | +|**IIS logs** | Collection only | Collection only | |**Multi-homing** | Collection only | Collection only | |**Application and service logs** | - | Collection only | |**Sysmon** | Collection only | Collection only | |
| service-connector | Quickstart Cli App Service Connection | https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/service-connector/quickstart-cli-app-service-connection.md | Use the Azure CLI [az webapp connection](/cli/azure/webapp/connection) command t - **App Service name:** the name of your App Service that connects to the target service. ```azurecli-interactive-az webapp connection list -g "<your-app-service-resource-group>" -n "<your-app-service-name>" +az webapp connection list -g "<your-app-service-resource-group>" -n "<your-app-service-name>" --output table ``` ## Next steps |