Hi @mjtd,

A few things to double‑check... Make sure you’re running in a Unity Catalog enabled workspace and that your source path is under a UC external location or volume, not just a raw storage URL. Auto Loader file notifications with managed file events are only supported on ADLS Gen2 (abfss://) and UC volumes over it. They are not supported on Azure Blob Storage (blob.core.windows.net). If your external location points at Blob, you’ll need to either move to ADLS Gen2 or fall back to directory listing/classic notifications.

Also, make sure your cluster is on Databricks Runtime 14.3 LTS or above.

If all of the above are true, and the test connection still fails with a queue.create error, checking the storage account’s Activity Log for failed queueServices/queues/write operations (and the caller identity) is the next best step.

If this answer resolves your question, could you mark it as “Accept as Solution”? That helps other users quickly find the correct fix.