Skip to main content
← All Comparisons

qURL™ vs Azure Blob Storage SAS

A signed token for a blob, or a way into the app itself.

An Azure SAS is a signed token appended to a blob URL. Whoever holds it gets the permissions it grants until it expires, and revoking one usually means a stored access policy, a key rotation or revoking every user delegation key. qURL shares a live app or folder from your machine, with one-time links, email invitations and per-person revocation.

Azure has three kinds of SAS, and they differ in who signs them and how they end. This page separates the person who issues the SAS from the person who uses it, then shows the qURL workflow for the same temporary handoff.

Hand over a file from the command line

qURL CLI
# Serve the folder on this machine only
python3 -m http.server 8000 --bind 127.0.0.1 --directory ./export
# In a second terminal: publish it and make a one-time link
qurl publish http://127.0.0.1:8000
qurl share <CRID> --ttl 1h --session-duration 30m

How qURL and Azure Blob Storage SAS differ

User delegation SAS. Signed with a user delegation key obtained with Microsoft Entra credentials, and limited by that user’s permissions. The key, and so the SAS, lasts at most 7 days. You revoke it by revoking the user delegation keys, which ends every user delegation SAS on the storage account, or by changing the signer’s role assignments; Microsoft notes there may be a delay before an existing SAS stops working.

Service SAS and account SAS. Both are signed with the storage account key. A service SAS can be tied to a stored access policy (up to five per container); deleting or changing the policy affects every SAS tied to it at once. An ad hoc SAS without a policy can be revoked immediately only by regenerating the account key that signed it, which breaks everything else signed with that key. Account SAS cannot use stored access policies.

Who holds it. Microsoft warns that a leaked SAS can be used by anyone who obtains it. Entra credentials identify the issuer, not the holder: Microsoft also says there is no direct way to identify which clients accessed a resource. A newer user delegation SAS option, sduoid (service version 2025-07-05 and later), binds the SAS to one Entra user, who must sign in with Entra to use it.

qURL. qurl publish registers an app, or a file server for a folder, on your machine. qurl share prints a link that opens once; qurl access invite lets one named email address in, after it verifies that mailbox and saves a passkey, with no Microsoft or LayerV account. Revoking one invitation leaves everyone else’s access alone.

The same handoff with qURL

  1. Start a file server for the folder, bound to 127.0.0.1, or skip this step for a running app.
  2. Publish it invite-only: no storage account and no key to manage.
  3. Invite the recipient. They open the invitation in a browser, verify the mailbox and save a passkey, with no Microsoft or LayerV account.
  4. For one quick look instead, publish without --access and send a link from qurl share <CRID> --ttl 1h.
  5. End one person’s access with qurl access revoke_invitation, or everyone’s with qurl stop <CRID> or qurl delete <CRID>. No key rotation, and nobody else is affected.
Hand over a folder to a named recipient
# Serve the folder on this machine only
python3 -m http.server 8000 --bind 127.0.0.1 --directory ./export
# In a second terminal: publish invite-only and invite the recipient
qurl publish http://127.0.0.1:8000 --access invite_only -o json
qurl access invite <CRID> --email recipient@example.com -o json

The three SAS types, and how each one ends

The three SAS types, and how each one ends
TypeSigned withLongest lifeHow to revoke it early
User delegation SASA user delegation key obtained with Entra credentials7 days, the key’s limitRevoke the account’s user delegation keys (all of them), or change the signer’s role assignments
Service SASThe storage account keyThe expiry you set, or the stored access policy’sDelete or change its stored access policy; without one, regenerate the account key
Account SASThe storage account keyThe expiry you setRegenerate the account key; stored access policies are not supported

Feature Comparison

FeatureqURLAzure Blob Storage SAS
What is sharedAn HTTP app or file server, by its originA blob, container or account, with the permissions in the SAS
Upload or copyNone: the data stays where it isThe data lives in a storage account
IssuerThe device that published the resourceAn Entra user (user delegation SAS) or whoever holds the account key
What the recipient needsA browser; an invited recipient verifies their mailbox and saves a passkey, with no accountThe SAS URL; with sduoid, an Entra sign-in as the named user
Recipient identifiedInvitation: the verified mailbox. One-time link: no, it is a bearer linkNot by default; sduoid binds a user delegation SAS to one Entra user
ReuseA qurl share link opens once; an invitation brings the same person backValid for the interval the SAS allows
ExpiryThe link at --ttl; the session separately, up to 24 hoursThe expiry you set; user delegation SAS at most 7 days
Revoking one grantRevoke one invitation; with an account, revoke one link through the APIPer stored access policy, or by key rotation or user delegation key revocation, which reach every SAS they cover
A transfer still running at expiryAt the session deadline, open requests and streams are cancelledNot stated in the checked Microsoft documentation

Which one to use

Choose qURL to

Give an outside recipient a file or a live app without a storage account, an Entra identity on their side, or a key rotation to take it back: invite their email, or send a link that opens once.

Already sending SAS links?

A SAS works for whoever holds it, and taking one back early often means rotating a key or revoking delegation keys that cover other links too. For files you produce locally or an app you are running, share with qURL instead: invite each person by email and revoke one invitation without touching anyone else’s.

qURL connects outbound, so you can share your app without opening an inbound port. Keep any other public routes to your app restricted. A link’s expiry controls when it can be opened; an opened session has its own duration. Explore access and revocation.

Frequently Asked Questions

Does a user delegation SAS identify the person who uses it?

Not by default. Entra credentials sign it, so it identifies the issuer, and the holder can be anyone who has the URL. The sduoid option binds it to one Entra user, who must sign in with Entra. A qURL invitation admits only the invited mailbox, with a passkey and no account.

How do I revoke one SAS?

Tie service SAS tokens to a stored access policy and delete or change the policy. Without a policy, Microsoft says regenerating the account key is the only way to revoke an ad hoc SAS immediately. User delegation SAS tokens end when you revoke the account’s user delegation keys. With qURL, revoke one invitation and everyone else keeps access.

How long can a SAS last?

A user delegation SAS lasts at most 7 days, the life of its key. Service and account SAS last as long as the expiry you set. A qURL link waits up to 24 hours to be opened without an account, or 30 days with one, and its session lasts up to 24 hours.

Who can open a qURL link?

Whoever holds it, once: with no flags, qurl share prints a single-use link. The documented browser flow starts a session for that browser, which lasts 1 hour by default for an app published from the CLI; another browser on the same public IP cannot use that browser session. A script or agent that opens the link without a browser can be admitted by its network address, which other devices on that public IP may share until the session ends. Keep your app’s own sign-in for anything sensitive. A link admits whoever opens it: the API’s IP and country rules do not apply to the signed links qurl share issues.

Hand over a file or an app without an account

Paste one prompt into your coding agent, or install the qURL CLI and publish the folder or app yourself. No bucket, no upload, no sign-up.

New to qURL? Start at qurl.link

Book a pilot

Tell us what to hide. We’ll scope a pilot.

Enterprise starts with a paid pilot on one application, typically 60 to 90 days, credited in full toward year one if you convert within 60 days. After that, an annual package sized to what you protect, not per seat.