Azure Architecture & Advisory
AZ-305 certified architecture and AZ-104 level operations for South African businesses and MSPs. Thirty years of enterprise IT behind every recommendation — delivered with the rigour of large-scale production environments, priced for a growing business.
Choose your country to see the rate card that applies to you.
Architecture & Design
Landing zones, identity, networking, compute, data platform and BCDR — designed against the Cloud Adoption and Well-Architected Frameworks.
Administration & Operations
Day-two Azure administration, Microsoft 365 deployments, hybrid environments, monitoring and cost control done properly.
Estate Deep Dives
Fixed-price, structured assessments of your Azure and Microsoft 365 estate, with a written report your exec team can act on.
View assessmentsSimple, Structured, No Guesswork
Every engagement starts with a free 30-minute discovery call so we both know it's a fit before you spend anything.
Free Discovery Call
Thirty minutes to understand your challenge, your estate and your constraints. No obligation.
Assess or Scope
Start with a fixed-price estate assessment, or scope a project or retainer directly — whichever fits.
Deliver & Support
Architecture, implementation guidance or hands-on delivery, with a written trail your team can act on.
Hourly Advisory
Architecture, review and guidance when you need a senior pair of eyes.
- AZ-305 and AZ-104 certified
- Remote or on-site (SA)
- No minimum retainer
Project-Based
Scoped deliverables at a fixed price, quoted after a discovery call.
- Clear scope and milestones
- Fixed price
- Assessment fee credited in
Monthly Retainer
Ongoing advisory and support for teams that want a senior architect on call.
- Agreed monthly hours
- Priority response
- MSP white-label available
The problems that bring an Azure architect in
Almost nobody phones asking for architecture. They phone because something specific has gone wrong, or because a decision is due and nobody wants to own it. These are the ones that come up most.
"The Azure bill keeps climbing"
Usually not a pricing problem. Usually a design problem that pricing is reporting.
- Oversized virtual machines from a lift-and-shift nobody revisited
- Storage tiers left on hot for data nobody has opened in two years
- Non-production environments running through the night and over weekends
- No tagging, so nothing can be attributed to a team or a client
- Reserved instances and savings plans never evaluated
"We grew into Azure without a plan"
The estate works, but nobody can explain why it is arranged the way it is.
- One subscription holding everything, or forty nobody can name
- Networking assembled peering by peering as needs arose
- No policy, so every new resource is a fresh negotiation
- Naming conventions that changed three times
- An Azure landing zone design that was started and abandoned
"Identity is the part that scares us"
The half of the estate where a mistake is quiet until it is very loud.
- Active Directory and Microsoft Entra ID out of step with each other
- Conditional access rules nobody wants to touch
- Standing administrative access that should be time-bound
- Guest and partner accounts accumulated over years
- A Copilot rollout about to inherit whatever the permissions actually are
How an engagement runs
Four steps, in the same order every time, because the expensive mistakes are almost always made before anyone touches a keyboard.
1. A free thirty-minute call. What you are running, what is hurting, what you already tried. At the end of it you get an honest answer about whether this is worth paying for — including, sometimes, that it is not, or that what you need is a different kind of supplier.
2. Look before recommending. For anything beyond a single question, the work starts with reading the estate as it is rather than as the documentation describes it. That is what the fixed-price estate assessments exist for: a health check where the scope is small, a deep dive where it is not. The assessment fee is credited against the work that follows, so looking first does not cost you twice.
3. A written design, not a conversation. You get a document: the current state, the recommended target, the decisions taken and why, the ones deliberately deferred, and a prioritised sequence. It is written so that an engineer who was not in the room can build from it, and so that a finance director who was not in the room can understand what is being bought.
4. Build, or hand over. I implement it, or your team does with me reviewing, or your MSP does under a white-label arrangement. All three are normal. What does not happen is a design that depends on me being there forever — if the handover does not work, the design was wrong.
What Azure consulting covers here
Architecture and governance. Azure landing zones, management group and subscription design, Azure Policy, role-based access control, tagging and cost attribution, naming standards, and the governance model that keeps them true after the consultant leaves.
Infrastructure and networking. Hybrid connectivity, network topology and segmentation, migration planning from on-premises estates, resilience and disaster recovery design, and infrastructure as code in Bicep and ARM so that what was built can be rebuilt.
Identity and security posture. Microsoft Entra ID design, hybrid identity, conditional access, privileged access, and the tenant-side work that decides what Microsoft 365 Copilot will and will not surface once it is switched on.
Microsoft 365 and Copilot readiness. Tenant configuration, migration and consolidation, oversharing review, and the AI exposure work that tells you what your staff are already putting into AI tools before you formalise anything.
Cost optimisation. Right-sizing, commitment modelling, environment scheduling, and the unglamorous attribution work that lets you tell which team or client is generating which line of the invoice.
One architect, named, verifiable
Engagements are delivered by Gustav Bam personally — AZ-305 Azure Solutions Architect Expert and AZ-104 Azure Administrator Associate, and a Microsoft Certified Trainer (MCT). Both certifications verify on Microsoft Learn; ask and the links come with the proposal. There is no bench, no handover to a junior after the sales call, and no team page full of people you will never meet.
Thirty years in enterprise infrastructure since 1996, most of it inside a large South African financial services group, running Exchange, SQL Server and Windows Server estates through consolidation and modernisation programmes. That matters mainly because the environments that need this work are rarely clean — they are twenty years of decisions made by people who have since left, and reading those is a different skill from designing on a blank page.