One provider, several workflows
Azure can cover multiple operational surfaces on Wodby instead of forcing teams to split cluster, storage, database, and mail concerns across several vendors.
Integration
Azure integrations on Wodby
Use Azure for several adjacent workflows on Wodby: AKS as a cluster target, Azure Blob for backup storage, and Azure Databases for managed relational services.
KubernetesStorageManaged DB
Keep credentials reusable
A shared provider account or access model can support several Wodby workflows at once.
Match managed services to app stacks
Teams can combine provider-managed infrastructure with Wodby stack-based application delivery.
Supported workflows
How Azure fits into Wodby
Each supported integration kind maps Azure into a specific part of the delivery workflow, whether that means pulling source code, running pipelines, relaying email, connecting managed services, or injecting provider credentials into workloads.
Kubernetes
Azure Kubernetes Service (AKS)
Use Azure as a managed Kubernetes target for Wodby stacks.
- Deploy the same versioned stack model onto a managed cluster target.
- Keep cluster operations with the provider while Wodby stays responsible for the app delivery workflow.
- Useful for teams that want managed infrastructure without rebuilding their stack definitions.
Storage
Azure Blob
Send backup archives and storage-backed data from Wodby services to Azure.
- A practical fit for stateful services that should keep backup archives outside the running environment.
- Works with automatic backup workflows and restore paths.
- Lets teams standardize on an object storage target without changing the app stack itself.
Managed DB
Azure Databases
Use managed database services from Azure with Wodby cloud database stacks.
- Useful when the database should be managed externally instead of running inside the application stack.
- The provider-backed database stays inside the same stack-aware workflow on Wodby.
- Most relevant to Cloud PostgreSQL, Cloud MySQL, and Cloud MariaDB stacks.
Related features
Explore the surrounding workflow
This provider usually sits next to stack-based delivery, backup workflows, managed databases, or integration-backed configuration. These pages cover the product surfaces most relevant to Azure.
Explore Kubernetes delivery
See how Wodby deploys versioned stacks onto managed Kubernetes targets.
See backups and imports
Use storage integrations as backup targets for stateful services and app data.
Explore managed databases
Connect cloud database stacks to managed providers while keeping the same app workflow.
Browse all integrations
Compare this provider with the rest of the integration catalog and other supported workflows.
Stack fit
Stacks that commonly pair with Azure
Wodby does not treat integrations as isolated setup screens. They become part of stack delivery, so the strongest matches are the stacks where this provider solves a repeated operational problem.
Next.js
Stack
Next.js application stack for frontend and full-stack projects that need a reusable deployment setup.
Next.js is a representative app stack when you want to deploy onto a managed Kubernetes target.
View stackLaravel
Stack
Laravel application stack for teams that want a reusable setup for web, worker, and queue-based PHP projects.
Laravel teams can keep the same stack model while moving the runtime onto a managed cluster.
View stackDrupal 11
Stack
Drupal 11 application stack for modern self-hosted websites and multi-environment Drupal delivery.
Drupal benefits from versioned stacks even when the cluster target is external Kubernetes.
View stackNode.js
Stack
Node.js application stack for APIs, workers, and custom services with a repeatable runtime setup.
Node.js services are a practical fit for cluster-based delivery when teams want runtime portability.
View stack
Compare providers or keep reading
Use the catalog to compare other providers with the same integration kind, or read the broader feature pages to understand how integrations fit into Wodby stacks, CI/CD, backups, and managed services.