Skip to content
Logs
Visit Logs on GitHub
Set theme to dark (⇧+D)

Enable Logpush to Microsoft Azure

Cloudflare Logpush supports pushing logs directly to Microsoft Azure via the Cloudflare dashboard or via API.

Manage via the Cloudflare dashboard

Enable Logpush to Microsoft Azure via the dashboard.

To enable the Cloudflare Logpush service:

  1. Log in to the Cloudflare dashboard.

  2. Select the Enterprise domain you want to use with Logpush.

  3. Go to Analytics > Logs.

  4. Click Connect a service. A modal window opens where you will need to complete several steps.

  5. Select the data set you want to push to a storage service.

  6. Select the data fields to include in your logs. You can add or remove fields later by modifying your settings in Logs > Logpush.

  7. Select Microsoft Azure.

  8. Enter or select the following destination information:

    • SAS URL
    • Blob container subpath (optional)
    • Daily subfolders
  9. Click Validate access.

  10. Enter the Ownership token (included in a file or log Cloudflare sends to your provider) and click Prove ownership. To find the ownership token, click the Open button in the Overview tab of the ownership challenge file.

  11. Click Save and Start Pushing to finish enabling Logpush.

Once connected, Cloudflare lists Microsoft Azure as a connected service under Logs > Logpush. Edit or remove connected services from here.

Manage via API

Cloudflare uses a service-level shared access signature (SAS) to gain access to your Blob Storage container. You'll need to provide Write permission and an expiration period of at least 5 years, which will allow you to not worry about the SAS token expiring.

Only roles with Cloudflare Log Share edit permissions can read and configure Logpush jobs because job configurations may contain sensitive information. Ensure Log Share permissions are enabled before attempting to read or configure a Logpush job.

To enable Logpush to Azure:

  1. Create a Blob Storage container. See instructions from Azure.

  2. Create a shared access signature (SAS). To learn about shared access signatures, see information from Azure. Logpush requires a service-level SAS, which provides the most restricted access. To create a service-level SAS, see instructions from Azure or use the Storage Explorer feature in your storage account portal. Select Storage Explorer, navigate to and then right-click on your blob container to see the Get Shared Access Signature option. Select that option, set an expiry time of at least 5 years, and select only Write permission.

  3. Provide the SAS URL when prompted by the Logpush API or UI.