Troubleshoot Universal Print Logs and Alerting (Preview)

This article helps you diagnose and resolve errors with the Logs and Alerting feature. Errors fall into two independent categories:

Category	When it happens	Where you see it
Configuration errors	When you save (or read) your alerting settings in the admin portal	An error message appears immediately after you select Save.
Pipeline status errors	After setup, while Universal Print streams telemetry to your Data Collection Rule (DCR)	The alerting status shows Error with a status message, even though the page loaded successfully.

Important

These two categories are independent. The configuration page can load successfully (no save error) and still show an alerting status of Error. A load success only means your settings were read; an Error status means telemetry is currently failing to reach your workspace.

Understand the alerting status

After you enable the feature, the Health information section on the Logs and alerts Overview page reports one of three statuses, shown with a Status message that adds detail:

Status	Meaning
Active	Alerting is enabled and the most recent upload to your workspace succeeded. The status message reads "Logs are being sent to your configured data collection endpoint."
Inactive	Alerting is enabled but telemetry isn't currently being delivered to your workspace.
Error	Alerting is enabled, but the most recent upload to your Data Collection Rule failed. The status message describes the cause.

The status reflects the health of the background pipeline that delivers telemetry to your workspace. An Error status doesn't undo your configuration — it tells you that data isn't currently flowing and that an action might be required to restore it.

No data or delayed data

If queries against the Universal Print tables return nothing, or data seems to lag, work through these checks before assuming an error.

Expected latency. Telemetry normally appears in your workspace within a few minutes of the underlying event. Right after you first enable the feature, allow extra time — the first records can take several minutes. The three custom tables (UniversalPrintPrinterHealth_CL, UniversalPrintJob_CL, UniversalPrintBillingSummary_CL) are created by the deployment in Step 2, so they exist before any data arrives — but they stay empty until the first upload succeeds, and a query returns no rows until then. Billing records are aggregated and arrive on a periodic roll-up rather than in real time.

Symptom	Likely cause	Fix
No data in any table after enabling	Feature not enabled in the portal, no matching activity yet, or the wrong DCR was selected.	Re-check Step 3; confirm the DCR name in the portal matches the one from Step 2 (default `dcrup-<workspace-name>`), print a test job, then wait a few minutes.
Workspace or DCR missing from the portal dropdowns	The enabling admin lacks read access to the workspace or DCR.	Grant at least Reader on the workspace and DCR (or the resource group that holds them) — see Azure permissions — then reopen the configuration page.
Only some categories have data	Not every category was selected, or there's been no activity of that type.	Confirm the categories you expect are selected in Step 3, and generate the relevant activity (print a job, change a printer).
Data stopped arriving after working previously	The pipeline status may show Error.	Check the alerting status and follow Pipeline status errors.

Configuration errors (when you save settings)

These errors appear immediately when you save your alerting settings. Find the message you received in the table below.

Error	What it means	How to fix
Feature not available	The Logs and Alerting feature isn't enabled for your tenant yet.	The feature is rolling out in preview. Contact your Universal Print representative to confirm availability for your tenant.
Invalid request	The settings couldn't be read.	Refresh the configuration page and try again.
Status can't be edited	You tried to change a value that Universal Print sets automatically.	Don't set the status field — it's read-only and managed by the service. Remove it and save again.
Invalid Log Analytics workspace resource ID	The workspace resource ID is missing or malformed.	Provide a valid workspace resource ID in the form `/subscriptions/<subscription-id>/resourceGroups/<resource-group>/providers/Microsoft.OperationalInsights/workspaces/<workspace-name>`.
Invalid Data Collection Rule resource ID	The DCR resource ID is missing or malformed.	Provide a valid DCR resource ID in the form `/subscriptions/<subscription-id>/resourceGroups/<resource-group>/providers/Microsoft.Insights/dataCollectionRules/<dcr-name>`.
Select at least one activity	You enabled alerting without choosing any data to collect.	Select at least one category — Printer activity, Job Activity, or Billing Event — before you save.
Can't access the Data Collection Rule	Universal Print couldn't validate the DCR. The DCR might not exist, might be missing the required configuration, or Universal Print might not have permission to publish to it.	Confirm the DCR exists, has the configuration created during setup, and that the Universal Print service principal has the Monitoring Metrics Publisher role on the DCR. Then save again. See Set up Logs and Alerting.
Workspace and DCR don't match	The workspace you supplied isn't the one the DCR is linked to.	Point the DCR at the intended workspace, or supply the workspace ID that matches the DCR.
Validation timed out	Validating the configuration took too long.	This is temporary. Wait a moment and save again.
Too many requests	Validation requests were throttled.	Wait a moment and save again.
Service temporarily unavailable	A dependency was briefly unavailable during validation.	Wait a moment and save again.
Settings were updated elsewhere	Another change to the same tenant settings was saved at the same time.	Reload the page to get the latest settings, then reapply your change.
Couldn't save settings / Something went wrong	An unexpected error occurred while validating or saving.	Try again. If the problem persists, contact support and reference "Logs and Alerting".

Tip

Most timeout, throttling, and "temporarily unavailable" errors are transient. Retrying after a short wait usually succeeds.

Pipeline status errors (Error status after setup)

When the alerting status shows Error, the accompanying message indicates why the most recent upload to your Data Collection Rule failed. Match the cause in the message to the table below.

Cause	What it means	How to fix
Authentication failure	Universal Print couldn't authenticate to your monitoring endpoint.	Usually transient. It self-recovers on the next successful upload. If it persists, contact support.
Permission denied	Universal Print no longer has permission to send logs to your Data Collection Rule.	Re-grant the Monitoring Metrics Publisher role to the Universal Print service principal on the DCR, then save your settings again to revalidate.
Not found	The Data Collection Rule or its endpoint can't be found. It might have been deleted or recreated.	Recreate or repoint the DCR (see Set up Logs and Alerting), then save your settings again.
Throttled	Log ingestion is being throttled, typically due to high volume.	This self-recovers as the backlog clears. If throttling is frequent, consider scaling your ingestion configuration.
Temporary delivery failure	A transient Azure Monitor ingestion problem.	No action needed. Delivery resumes automatically on the next successful upload.

How an Error status clears

You generally don't need to manually reset the status. An Error status clears in either of these ways:

Automatically on the next successful upload to your workspace.
Immediately when you save your settings again — saving is treated as confirmation that you've addressed the problem and triggers a fresh validation.

So after you fix the underlying cause (for example, re-grant permission on the DCR or recreate a deleted DCR), save your alerting settings again to force revalidation. The status returns to Active once telemetry flows successfully.

Recovery checklist

If alerting shows Error and isn't recovering on its own, work through these steps:

Confirm the Data Collection Rule still exists in your subscription and that its resource ID matches what's configured in the portal.
Confirm the Log Analytics workspace still exists and is linked to that DCR.
Confirm the Universal Print service principal has the Monitoring Metrics Publisher role on the DCR. Re-grant it if it's missing — see Set up Logs and Alerting.
Save your alerting settings again to revalidate and clear the error.
Wait a few minutes, then run a sample query to confirm new data is arriving. See Monitor and report on print activity.
If the status stays in Error, contact support and reference "Logs and Alerting".