![]() ![]() Azure Update Management users should use the same workspace for Update Compliance.Desktop Analytics users should use the same workspace for Update Compliance.Although an Azure subscription is required, you won't be charged for ingestion of Update Compliance data. Choose an existing or configure a new Log Analytics Workspace, ensuring it is in a Compatible Log Analytics region from the following table.The solution was published by Microsoft and named WaaSUpdateInsights. ![]() Go to the Update Compliance page in the Azure Marketplace.Update Compliance has been replaced by Windows Update for Business reports for monitoring compliance of updates. The instructions below are listed for verification and troubleshooting purposes only for existing Updates Compliance users. Update Compliance is deprecated and no longer accepting any new onboarding requests. For the following steps, you must have either an Owner or Contributor Azure role as a minimum in order to add the solution. Update Compliance is offered as an Azure Marketplace application that is linked to a new or existing Azure Log Analytics workspace within your Azure subscription. This prerequisite will be enforced for Update Compliance starting on October 15, 2022.Īdd Update Compliance to your Azure subscription Azure AD device join or hybrid Azure AD join: All devices enrolled in Update Compliance must meet all prerequisites for enabling Windows diagnostic data processor configuration, including the Azure AD join requirement.The steps are outlined in Configuring Devices for Update Compliance. Showing device names in Update Compliance: For Windows 10, version 1803 or later, device names won't appear in Update Compliance unless you individually opt-in devices by using policy.These endpoints are enumerated in detail at Configuring Devices for Update Compliance manually. Data transmission requirements: Devices must be able to contact specific endpoints required to authenticate and send diagnostic data.To learn more about what's included in different diagnostic levels, see Diagnostics, feedback, and privacy in Windows. Some queries in Update Compliance require devices to send diagnostic data at Optional level (previously Full) for Windows 11 devices or Enhanced level for Windows 10 devices. Diagnostic data requirements: Update Compliance requires devices to send diagnostic data at Required level (previously Basic).Update Compliance counts Windows Insider Preview devices, but doesn't currently provide detailed deployment insights for them. Compatible Windows client servicing channels: Update Compliance supports Windows client devices on the General Availability Channel and the Long-term Servicing Channel (LTSC).Update Compliance only provides data for the standard Desktop Windows client version and isn't currently compatible with Windows Server, Surface Hub, IoT, or other versions. Update Compliance supports both the typical Windows 10 or Windows 11 Enterprise edition, and Windows 10 Enterprise multi-session. Compatible operating systems and editions: Update Compliance works only with Windows 10 or Windows 11 Professional, Education, and Enterprise editions.Update Compliance is available in the Azure Commercial cloud, but not available for GCC High or United States Department of Defense customers.īefore you begin the process to add Update Compliance to your Azure subscription, first ensure you can meet the prerequisites: For a list of GCC offerings for Microsoft products and services, see the Microsoft Trust Center. You should be aware that Update Compliance doesn't meet US Government community compliance (GCC) requirements. Update Compliance is a Windows service hosted in Azure that uses Windows diagnostic data. Before or as devices appear, you can learn how to Use Update Compliance to monitor Windows Updates and Delivery Optimization. For more information, see the enrollment section. Configure devices to send data to Update Compliance.Īfter you add the solution to Azure and configuring devices, it can take some time before all devices appear.Add Update Compliance to your Azure subscription.Ensure you can meet the requirements to use Update Compliance.The following steps cover the enrollment and device configuration workflow. This article introduces the high-level steps required to enroll to the Update Compliance solution and configure devices to send data to it. For more information, see Windows diagnostic data processor changes. Changes have been made to the Windows diagnostic data processor configuration.Support for Update Compliance will end on Mawhen the service will be retired. If you're currently using Update Compliance, you can continue to use it, but you can't change your CommercialID. Update Compliance has been replaced by Windows Update for Business reports. Update Compliance is deprecated and is no longer accepting new onboarding requests. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |