Merge branch 'main' of https://github.com/seesharprun/azure-docs-pr into cosmos-db-emulator-reference

Author: seesharprun

articles/active-directory/reports-monitoring/reports-faq.yml

@@ -106,6 +106,11 @@ sections:
         answer: |
           With passwordless authentication, User IDs appear as the username. To confirm this scenario, look at the details of the sign-in event in question. The *authenticationDetail* field will say *passwordless*.
 
+      - question: |
+          I see a 90025 error in the sign in logs. Does this mean my user failed to sign in? Has my tenant hit a throttling limit?
+        answer: |
+          No, in general 90025 errors are resolved by an automatic retry without the user noticing the error. This error can occur when an internal Azure AD subservice hits its retry allowance and does not indicate your tenant is being throttled. These errors are usually resolved by Azure AD internally without any user impact. If the user is unable to sign in due to this error, manually trying again should resolve the issue. 
+
   - name: Conditional Access
     questions:
       - question: |
@@ -165,4 +170,4 @@ sections:
           I keep getting permissions errors when running queries. I thought I had the appropriate role.
         answer: |
           You may need to sign in to Microsoft Graph separately from the Azure portal. Select your profile icon on the upper-right corner and sign in to the right directory.
-          You may be trying to run a query that you don't have permissions for. Select **Modify Permissions** and select the **Consent** button. Follow the sign-in prompts.
+          You may be trying to run a query that you don't have permissions for. Select **Modify Permissions** and select the **Consent** button. Follow the sign-in prompts.

articles/azure-arc/servers/prerequisites.md

@@ -2,7 +2,7 @@
 title: Connected Machine agent prerequisites
 description: Learn about the prerequisites for installing the Connected Machine agent for Azure Arc-enabled servers.
 ms.date: 01/25/2023
-ms.topic: conceptual 
+ms.topic: conceptual
 ---
 
 # Connected Machine agent prerequisites
@@ -44,7 +44,7 @@ Azure Arc supports the following Windows and Linux operating systems. Only x86-6
 * Debian 10 and 11
 * CentOS Linux 7 and 8
 * Rocky Linux 8
-* SUSE Linux Enterprise Server (SLES) 12 and 15
+* SUSE Linux Enterprise Server (SLES) 12 SP3-SP5 and 15
 * Red Hat Enterprise Linux (RHEL) 7, 8 and 9
 * Amazon Linux 2
 * Oracle Linux 7 and 8
@@ -131,3 +131,4 @@ You can also register the resource providers in the [Azure portal](../../azure-r
 
 * Review the [networking requirements for deploying Azure Arc-enabled servers](network-requirements.md).
 * Before you deploy the Azure Arc-enabled servers agent and integrate with other Azure management and monitoring services, review the [Planning and deployment guide](plan-at-scale-deployment.md).* To resolve problems, review the [agent connection issues troubleshooting guide](troubleshoot-agent-onboard.md).
+

articles/azure-monitor/logs/computer-groups.md

@@ -4,25 +4,24 @@ description: Computer groups in Azure Monitor allow you to scope log queries to
 ms.topic: conceptual
 author: bwren
 ms.author: bwren
-ms.date: 10/20/2021
+ms.date: 03/14/2023
 
 ---
 
 # Computer groups in Azure Monitor log queries
-Computer groups in Azure Monitor allow you to scope [log queries](./log-query-overview.md) to a particular set of computers.  Each group is populated with computers either using a query that you define or by importing groups from different sources.  When the group is included in a log query, the results are limited to records that match the computers in the group.
+Computer groups in Azure Monitor allow you to scope [log queries](./log-query-overview.md) to a particular set of computers.  Each group is populated with computers using a query that you define.  When the group is included in a log query, the results are limited to records that match the computers in the group.
 
 [!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-log-analytics-rebrand.md)]
 
 ## Creating a computer group
-You can create a computer group in Azure Monitor using any of the methods in the following table.  Details on each method are provided in the sections below. 
+You can create a computer group in Azure Monitor using the methods in the following table.  Details on each method are provided in the sections below. 
 
 | Method | Description |
 |:--- |:--- |
 | Log query |Create a log query that returns a list of computers. |
-| Log Search API |Use the Log Search API to programmatically create a computer group based on the results of a log query. |
-| Active Directory |Automatically scan the group membership of any agent computers that are members of an Active Directory domain and create a group in Azure Monitor for each security group. (Windows machines only)|
-| Configuration Manager | Import collections from Microsoft Configuration Manager and create a group in Azure Monitor for each. |
-| Windows Server Update Services |Automatically scan WSUS servers or clients for targeting groups and create a group in Azure Monitor for each. |
+| Active Directory | No longer supported |
+| Configuration Manager | No longer supported |
+| Windows Server Update Services | No longer supported |
 
 ### Log query
 Computer groups created from a log query contain all of the computers returned by a query that you define.  This query is run every time the computer group is used so that any changes since the group was created is reflected.  
@@ -37,44 +36,34 @@ Use the following procedure to create a computer group from a log search in the
 
 1. Click **Logs** in the **Azure Monitor** menu in the Azure portal.
 1. Create and run a query that returns the computers that you want in the group.
-1. Click **Save** at the top of the screen.
-1. Change **Save as** to **Function** and select **Save this query as a computer group**.
+1. Click **Save** at the top of the screen, and select **Save as function** from the dropdown.
+1. Select **Save as computer group**.
 1. Provide values for each property for the computer group described in the table and click **Save**.
 
 The following table describes the properties that define a computer group.
 
 | Property | Description |
 |:---|:---|
-| Name   | Name of the query  to display in the portal. |
-| Function alias | A unique alias used to identify the computer group in a query. |
-| Category       | Category to organize the queries in the portal. |
+| Function name   | Name of the query to display in the portal. |
+| Legacy category       | Category to organize the queries in the portal. |
+| Parameters | Add a parameter for each variable in the function that requires a value when it's used. For more information, see [Function parameters](functions.md#function-parameters). |
 
 
 ### Active Directory
-When you configure Azure Monitor to import Active Directory group memberships, it analyzes the group membership of any Windows domain joined computers with the Log Analytics agent.  A computer group is created in Azure Monitor for each security group in Active Directory, and each Windows computer is added to the computer groups corresponding to the security groups they are members of.  This membership is continuously updated every 4 hours.  
-
-> [!NOTE]
-> Imported Active Directory groups only contain Windows machines.
-
-You configure Azure Monitor to import Active Directory security groups from the **Legacy computer groups** menu item in your Log Analytics workspace in the Azure portal.  Select the **Active Directory** tab, and then **Import Active Directory group memberships from computers**.  When groups have been imported, the menu lists the number of computers with group membership detected and the number of groups imported.  You can click on either of these links to return the **ComputerGroup** records with this information.
+No longer supported
 
 ### Windows Server Update Service
-When you configure Azure Monitor to import WSUS group memberships, it analyzes the targeting group membership of any computers with the Log Analytics agent.  If you are using client-side targeting, any computer that is connected to Azure Monitor and is part of any WSUS targeting groups has its group membership imported to Azure Monitor. If you are using server-side targeting, the Log Analytics agent should be installed on the WSUS server in order for the group membership information to be imported to Azure Monitor.  This membership is continuously updated every 4 hours. 
-
-You configure Azure Monitor to import WSUS groups from the **Legacy computer groups** menu item in your Log Analytics workspace in the Azure portal.  Select the **Windows Server Update Service** tab, and then **Import WSUS group memberships**.  When groups have been imported, the menu lists the number of computers with group membership detected and the number of groups imported.  You can click on either of these links to return the **ComputerGroup** records with this information.
+No longer supported
 
 ### Configuration Manager
-When you configure Azure Monitor to import Configuration Manager collection memberships, it creates a computer group for each collection.  The collection membership information is retrieved every 3 hours to keep the  computer groups current. Before you can import Configuration Manager collections, you must [connect Configuration Manager to Azure Monitor](collect-sccm.md).  
-
-You configure Azure Monitor to import WSUS groups from the **Legacy computer groups** menu item in your Log Analytics workspace in the Azure portal.  Select the **System Center Configuration Manager** tab, and then **Import Configuration Manager collection memberships**. When collections have been imported, the menu lists the number of computers with group membership detected and the number of groups imported.  You can click on either of these links to return the **ComputerGroup** records with this information.
+No longer supported
 
 ## Managing computer groups
-You can view computer groups that were created from a log query or the Log Search API from the **Legacy computer groups** menu item in your Log Analytics workspace in the Azure portal.  Select the **Saved Groups** tab to view the list of groups.  
-
-Click the **x** in the **Remove** column to delete the computer group.  Click the **View members** icon for a group to run the group's log search that returns its members.  You can't modify a computer group but instead must delete and then recreate it with the modified settings.
+You can view computer groups that were created from a log query from the **Legacy computer groups** menu item in your Log Analytics workspace in the Azure portal.  Select the **Saved Groups** tab to view the list of groups.  
 
-![Saved computer groups](media/computer-groups/configure-saved.png)
+Click the **Run query** icon for a group to run the group's log search that returns its members.  Click the **Delete** icon to delete the computer group.  You can't modify a computer group but instead must delete and then recreate it with the modified settings.
 
+:::image type="content" source="media/computer-groups/configure-saved.png" alt-text="Screenshot of a Log Analytics resource in Azure with Legacy computer groups pane,  Saved Groups tab, Run query icon, and Delete icon highlighted." lightbox="media/computer-groups/configure-saved.png":::
 
 ## Using a computer group in a log query
 You use a Computer group created from a log query in a query by treating its alias as a function, typically with the following syntax:
@@ -89,33 +78,5 @@ For example, you could use the following to return UpdateSummary records for onl
 UpdateSummary | where Computer in (mycomputergroup)
 ```
 
-Imported computer groups and their included computers are stored in the **ComputerGroup** table.  For example, the following query would return a list of computers in the Domain Computers group from Active Directory. 
-
-```kusto
-ComputerGroup | where GroupSource == "ActiveDirectory" and Group == "Domain Computers" | distinct Computer
-```
-
-The following query would return UpdateSummary records for only computers in Domain Computers.
-
-```kusto
-let ADComputers = ComputerGroup | where GroupSource == "ActiveDirectory" and Group == "Domain Computers" | distinct Computer;
-  UpdateSummary | where Computer in (ADComputers)
-```
-
-## Computer group records
-A record is created in the Log Analytics workspace for each computer group membership created from Active Directory or WSUS.  These records have a type of **ComputerGroup** and have the properties in the following table.  Records are not created for computer groups based on log queries.
-
-| Property | Description |
-|:--- |:--- |
-| `Type` |*ComputerGroup* |
-| `SourceSystem` |*SourceSystem* |
-| `Computer` |Name of the member computer. |
-| `Group` |Name of the group. |
-| `GroupFullName` |Full path to the group including the source and source name. |
-| `GroupSource` |Source that group was collected from. <br><br>ActiveDirectory<br>WSUS<br>WSUSClientTargeting |
-| `GroupSourceName` |Name of the source that the group was collected from.  For Active Directory, this is the domain name. |
-| `ManagementGroupName` |Name of the management group for SCOM agents.  For other agents, this is AOI-\<workspace ID\> |
-| `TimeGenerated` |Date and time the computer group was created or updated. |
-
 ## Next steps
 * Learn about [log queries](./log-query-overview.md) to analyze the data collected from data sources and solutions.