Post 'extend' operator: Failed to resolve table or column expression named 'WaaSDeploymentStatus'...

[Subhayu2016]

Describe the bug
A clear and concise description of what the bug is. 'extend' operator: Failed to resolve table or column expression named 'WaaSDeploymentStatus'...

Post uploading to Intune Portal reporting getting error and Update Compliance Table not getting created

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots

Additional context
Add any other context about the problem here.

[hanenChh]

i have the same pb

[Ioan-Popovici]

You have to actually send update data to log analytics in order for that table to be created as stated in the blog post.

Enable Windows diagnostics

[MP-feedback]

I have the same problem, I had created the diagnostic settings and even left them for a week, however I don't see that table in the Log Analytics Workspace:

Currently we only have an Update ring, and Driver update policy assigned. We also have a feature update policy that hasn't been assigned and nothing under the quality updates tab. Do we need to create a quality update/expedite update policy for this table to show up in the Intune logs or does the WaaSDeploymentStatus table come from somewhere else?

I'm asking because I don't see that log listed here https://learn.microsoft.com/en-us/mem/intune/fundamentals/review-logs-using-azure-monitor#send-logs-to-azure-monitor

[Ioan-Popovici]

Ensure the devices are correctly configured to send Windows Update reporting data to Log Analytics

1. Go to the Microsoft Endpoint Manager Admin Center:
   • Navigate to Reports > Windows updates.
   • Verify that the reporting data collection for Windows Update for Business (WUfB) is enabled.
2. Ensure that Update compliance settings are configured:
   • Log in to the Azure portal.
   • Go to Azure Monitor > Log Analytics Workspaces > Workspace Settings.
   • Under Agents Management, ensure devices are correctly connected to the workspace.

Ensure that Update compliance settings are configured:
• Log in to the Azure portal.
• Go to Azure Monitor > Log Analytics Workspaces > Workspace Settings.
• Under Agents Management, ensure devices are correctly connected to the workspace.

Check Intune Device Configuration Policy for Update Compliance
The Update Compliance integration requires a Custom Device Configuration profile in Intune.

1. Go to Endpoint Manager Admin Center > Devices > Configuration Profiles.
2. Create or verify the following:
   • OMA-URI Configuration:
   • OMA-URI Path: ./Vendor/MSFT/Policy/Config/Update/AllowWUfBCloudProcessing
   • Value: 1
   This ensures Windows Update for Business telemetry data is sent to Azure.
3. Ensure the policy is deployed to the correct device group.

Verify Device Telemetry Settings
The WaaSDeploymentStatus data relies on telemetry. Ensure devices have the proper diagnostic data settings:

1. Open Settings on the device:
   • Go to Privacy > Diagnostics & Feedback.
   • Ensure that Optional diagnostic data is enabled.
2. In Intune:
   • Go to Devices > Windows > Configuration profiles.
   • Create or update a profile to set:
   • Telemetry level to Enhanced or Full.

Custom OMA-URI for Telemetry Settings
If required, deploy the following setting via a custom configuration profile:
• OMA-URI Path: ./Vendor/MSFT/Policy/Config/System/AllowTelemetry
• Value: Enhanced (2) or Full (3).

Verify Devices are Reporting to Log Analytics

1. Go to your Log Analytics Workspace in the Azure Portal.
2. Use the following query to check for data:
   ,,,
   UpdateCompliance
   | summarize count() by DeviceName
   ,,,

If no data is returned:
• Confirm the workspace ID and key are correct in your configuration.
• Ensure that devices can communicate with the Log Analytics endpoint.

Check for Windows Update Compliance Delay
• Windows Update reporting can take up to 24-48 hours to appear in Log Analytics.
• Devices must have internet connectivity and Telemetry Services running.

Validate Required Firewall and Network Connectivity

Devices must reach Log Analytics endpoints and Windows Update for Business (WUfB) telemetry endpoints. Allow the following URLs in your firewall/proxy:
• *.monitor.azure.com
• *.ods.opinsights.azure.com
• *.loganalytics.io
• v20.events.data.microsoft.com

Revalidate Device Enrollment
Devices must be enrolled in both Intune and correctly configured for WUfB.

Run the following commands on a client machine to validate settings:

# Check Telemetry Level
Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection"

# Check Connectivity to Windows Update Service
Test-NetConnection -ComputerName settings-win.data.microsoft.com -Port 443

[MP-feedback]

Hi Ioan,

I had some questions about some of these steps, I have written them inline below:

Ensure the devices are correctly configured to send Windows Update reporting data to Log Analytics
1. Go to the Microsoft Endpoint Manager Admin Center:

• Navigate to Reports > Windows updates.

• Verify that the reporting data collection for Windows Update for Business (WUfB) is enabled.

I do see reports here, but I'm not sure what you mean "Verify that the reporting data collection for Windows Update for Business (WUfB) is enabled." or what exactly I'm looking for as under this section I can see:

2. Ensure that Update compliance settings are configured:
   • Log in to the Azure portal.
   • Go to Azure Monitor > Log Analytics Workspaces > Workspace Settings.
   • Under Agents Management, ensure devices are correctly connected to the workspace.

I installed the agent on two devices but the WaaSDeploymentStatus table is still not created,

do I need to create a DCR, and if so what do I choose for Data collection endpoint? Or resources?

Check Intune Device Configuration Policy for Update Compliance
The Update Compliance integration requires a Custom Device Configuration profile in Intune.
1. Go to Endpoint Manager Admin Center > Devices > Configuration Profiles.
2. Create or verify the following:
• OMA-URI Configuration:
• OMA-URI Path: ./Vendor/MSFT/Policy/Config/Update/AllowWUfBCloudProcessing
• Value: 1
This ensures Windows Update for Business telemetry data is sent to Azure.
3. Ensure the policy is deployed to the correct device group.

I am wondering if this can be re-created on a new tenant (one impacted by GDPR*) now that update compliance has been replaced by WUFB Reporting? Is this accurate, this setting does not seem to be a thing anymore:

https://learn.microsoft.com/en-us/windows/client-management/mdm/policy-csp-system#allowwufbcloudprocessing

Verify Device Telemetry Settings
The WaaSDeploymentStatus data relies on telemetry. Ensure devices have the proper diagnostic data settings:
1. Open Settings on the device:
• Go to Privacy > Diagnostics & Feedback.
• Ensure that Optional diagnostic data is enabled.
2. In Intune:
• Go to Devices > Windows > Configuration profiles.
• Create or update a profile to set:
• Telemetry level to Enhanced or Full.

I had to create a GPO as another GPO was setting this to =1, however even with =3 set the table is still not created

Custom OMA-URI for Telemetry Settings
If required, deploy the following setting via a custom configuration profile:
• OMA-URI Path: ./Vendor/MSFT/Policy/Config/System/AllowTelemetry
• Value: Enhanced (2) or Full (3).

Verify Devices are Reporting to Log Analytics
1. Go to your Log Analytics Workspace in the Azure Portal.
2. Use the following query to check for data:
,,,
UpdateCompliance
| summarize count() by DeviceName
,,,

There is also no table named UpdateCompliance, again I am wondering if this works on a new tenant (one impacted by GDPR*) now that UpdateCompliance has been renamed to WUFB reporting?

If no data is returned:
• Confirm the workspace ID and key are correct in your configuration.

I think the workspace ID and key are correct because if I click this link and run the query it generated I see

• Ensure that devices can communicate with the Log Analytics endpoint.
Check for Windows Update Compliance Delay
• Windows Update reporting can take up to 24-48 hours to appear in Log Analytics.
• Devices must have internet connectivity and Telemetry Services running.
Validate Required Firewall and Network Connectivity
Devices must reach Log Analytics endpoints and Windows Update for Business (WUfB) telemetry endpoints. Allow the following URLs in your firewall/proxy:
• *.monitor.azure.com
• *.ods.opinsights.azure.com
• *.loganalytics.io
• v20.events.data.microsoft.com
Revalidate Device Enrollment
Devices must be enrolled in both Intune and correctly configured for WUfB.
Run the following commands on a client machine to validate settings:

Check Telemetry Level

Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection"

Check Connectivity to Windows Update Service

Test-NetConnection -ComputerName settings-win.data.microsoft.com -Port 443

Any idea why this registry key would not be getting set?

As I understand it this was replaced with this setting

I see it getting set at this reg key instead:

Thank you in advance for your help on this.

[MP-feedback]

It looks like that table is not a thing anymore:

I have started updating the v8.0 table to use the new logs, but before I finish it I thought I would ask if you guys will also be updating it?