LowCodeStacks™
Sign in

Guides · 119

What are you trying to do?

Fix a problem

5The error or symptom in front of you, and the fix.

  • Data & storage

    Azure Blob tiers and a lifecycle management policy without the early-deletion bill

    Cool, cold and archive cost less per gigabyte and each has a minimum stay, 30, 90 and 180 days, charged pro rata when a blob is deleted, overwritten or moved earlier. A lifecycle management policy runs once a day and takes up to a day to start. The tier to upload into, the rules that don't bounce blobs back and forth, how last-access tracking works, and what archive really costs in time.

  • Data & storage

    Azure Blob storage 403 not authorized, decoded: permission mismatch, network block, shared key or SAS

    Every Blob storage 403 carries a second code that says which of four things refused it: AuthorizationPermissionMismatch (the identity or SAS lacks a data permission), AuthorizationFailure (a firewall, private endpoint or network rule), KeyBasedAuthenticationNotPermitted (shared key is off), or a SAS that's wrong in a field. What each means, the role that fixes it, the waits, and the DNS check most people skip.

  • Data & storage

    Azure SQL serverless: the first connection fails with error 40613, and the auto-pause settings behind it

    A paused serverless database answers its first connection with error 40613 and resumes in the background, usually within a minute; everything after that is about retries and the auto-pause delay. The retry settings per driver that ride out the resume, what stops a database pausing at all, how to see the sessions holding it open, and when serverless costs more than provisioned.

  • Data & storage

    Cosmos DB 429 request rate too large: when it is fine, and how to find the hot partition

    A 429 from Cosmos DB means one second's request units ran out. If 1 to 5 percent of requests get one and latency is fine, that's a full tank, not a fault, and the SDKs retry up to nine times before your app hears about it. Above that, the cause is total load, a hot partition, metadata calls or a transient error, each with its own fix. The metrics to open, the log query that names the partition key, and what autoscale does and doesn't do.

  • Data & storage

    Power Apps to Azure SQL with Entra ID, not a shared connection: the secure setup

    The SQL Server connector signs in four ways and only Microsoft Entra ID Integrated tells the database who the user is; a shared SQL login is client-side security, whatever filters the app has. The setup: an Entra admin on the server, database users from the external provider, row-level security on the signed-in name, secure implicit connections for the apps that must keep a login, and the delegation limits to design around.

Choose a tool

1Decide before you build.