Microsoft partner practice — Azure, Fabric, Copilot and Power BI delivery.
Microsoft is the stack most South African enterprises already own, which makes it the fastest place to put AI into real work — and the easiest place to waste a licence. We build Azure and Microsoft Fabric data platforms, roll out Microsoft 365 Copilot so that people actually use it, and build governed agents in Copilot Studio and Microsoft Foundry.
Most of the organisations we meet in Johannesburg and Cape Town did not choose Microsoft for AI. They chose Microsoft years ago for email, Office and Active Directory, and AI arrived inside a licence they were already paying for. That is a real advantage: the identity model, the compliance posture and the data are already in one place. It is also the reason Microsoft AI projects fail in a particular way — the licences get bought, a pilot group is enthusiastic for three weeks, and nobody can say what changed.
Microsoft has had enterprise-grade datacentres in South Africa since 2019, when Azure went live in Johannesburg (South Africa North) and Cape Town (South Africa West) — the first from a global provider anywhere on the continent. Availability Zones followed in the Johannesburg region in 2021. So the infrastructure question for most South African workloads is settled, and the interesting questions have moved up the stack: where does the model actually run, who owns an agent, and what does it cost per month once 400 people are using it.
The residency question deserves a straight answer, because it is the one we are asked in every financial-services meeting and the one most vendor pages blur. Data at rest is committed: Microsoft lists South Africa among the countries where Copilot Cowork stores the content of interactions — prompts and responses — in-country when a tenant's default geography is South Africa. Processing is a different matter. Microsoft's November 2025 sovereignty announcement named South Africa among eleven countries due to get in-country processing for Microsoft 365 Copilot interactions during 2026; an editor's update to that same post on 3 April 2026 narrowed the near-term scope to Australia, India, the UAE, the UK and the US by the end of 2026, with Canada in 2027 and Japan in 2028. South Africa is not named in that revised timeline. That is not a reason to avoid Copilot. It is a reason to document the inference path with your information officer up front rather than discover it in an audit.
Our practice covers the whole lifecycle: Azure and Microsoft Fabric platform architecture, migrations off on-premise SQL Server, Power BI semantic models that stop three teams arguing about one number, Microsoft 365 Copilot adoption programmes, and custom agents in Copilot Studio and Microsoft Foundry. We are also an independent member of Anthropic's Claude Partner Network, which matters here more than it used to — Claude models are now generally available inside both Microsoft Foundry and Copilot Studio, so we can build on the Microsoft platform without being limited to one model vendor's roadmap.
Lakehouse and warehouse architecture on Microsoft Fabric and OneLake, or Azure Data Factory and Synapse where an estate already lives there — with workspace design, capacity sizing and role-based access defined before the first pipeline runs.
SQL Server, Oracle and legacy SSIS estates moved into Azure SQL, Fabric or a lakehouse, with automated reconciliation against the old reports so that month-end never notices the cut-over.
Power BI Premium on a governed semantic model, so revenue means one thing in every dashboard, every export and every agent that queries it. Row-level security and certified datasets included, not retrofitted.
The part most programmes skip: readiness work on SharePoint permissions and oversharing, a scoped pilot with measured baselines, role-based enablement, and a licence review at 90 days that tells you honestly who should keep a seat.
Custom agents grounded in SharePoint, Dataverse, Fabric data agents and MCP servers, published to Teams, the web or a native app — with evaluations and test sets so quality is measured rather than assumed.
Entra Agent ID, Agent 365 inventory, DLP and Conditional Access scoped per agent, plus Copilot credit forecasting and capacity monitoring so an agent that works in a demo also works in a rand-denominated budget.
Microsoft's AI surface has expanded faster than most buying committees can track, and several pieces overlap. Here is the stack as it stands in September 2026, what each part is genuinely for, and where the boundaries sit.
The assistant embedded in Word, Excel, PowerPoint, Outlook and Teams, grounded in your tenant through Microsoft Graph. It is per-user licensed and it answers, drafts and summarises inside the app you are already in. Strong on the daily grind of a knowledge worker; it is not the thing that automates a business process end to end.
Microsoft's agentic layer for knowledge workers, and a different product from the in-app assistant despite the shared name. You describe an outcome and Cowork carries out multi-step work across apps — drafting documents, building spreadsheets and decks, scheduling, posting in Teams, running deep research — grounded by Work IQ. Sensitive actions such as sending an email pause for your approval, and every action is auditable.
Where you build your own agents. Ground them in SharePoint, Dataverse, Fabric data agents, Bing Custom Search or an MCP server; publish to Teams, a website or a native app via the client SDK; and evaluate them against test sets. This is the tool that turns Copilot from an assistant into a business process.
Copilot Studio is no longer single-vendor. Anthropic's Claude models reached general availability globally in March 2026, and since June 2026 you can select Claude Sonnet 5 or GPT-5.5 Chat as an agent's primary model, with Mistral and xAI available as further options. Model choice per agent is now a cost and quality lever rather than a procurement argument.
Computer use lets an agent drive browsers and desktop applications on a Windows 365 cloud PC when a system has no API — the honest answer for the legacy line-of-business software most South African estates still run. The agent-to-agent protocol lets a front-door agent delegate to specialists rather than becoming one unmaintainable mega-agent.
Every agent now gets its own identity. Since July 2026 Copilot Studio creates an Entra Agent ID for every new agent automatically and the environment-level opt-out is gone. That is a governance shift, not a feature: connector permissions, Conditional Access and DLP now scope to an individual agent, and your agents show up in the same directory as your people.
The control plane for agents, licensed separately at 15 US dollars per user per month. It gives IT one inventory of every agent in the organisation — Microsoft-built, open-source or third-party — with permissions, behaviour and activity in one place. Worth understanding before you have forty agents, not after.
The developer platform, formerly Azure AI Foundry. Foundry Agent Service orchestrates multi-step agents with a model as the reasoning core; Foundry IQ handles retrieval; Foundry Control Plane runs continuous evaluations and can block a response that breaks a rule before it reaches a user. This is where custom, high-volume or customer-facing AI belongs.
Anthropic's models hosted on Azure, reached through your existing Azure account with Entra ID authentication and Azure role-based access control. Inference runs in Azure with a choice of Global or US data zones, zero data retention is available for sensitive workloads, and usage bills as Claude Consumption Units on the Azure invoice with MACC drawdown. It follows the Microsoft, NVIDIA and Anthropic partnership announced in November 2025.
Fabric unifies ingestion, lakehouse, warehouse, real-time intelligence and Power BI on OneLake under one capacity. Fabric IQ is the shared context layer that grounds agents in business meaning rather than raw tables, and Fabric data agents now surface into Microsoft Foundry over MCP as tools a Foundry agent can call — with traces visible in Foundry Observability.
The context services underneath the rest. Work IQ exposes real-time signal from Microsoft 365 files, mail, meetings and chats; Microsoft IQ connects that organisational context to agents built in Copilot Studio. Context, not model size, is usually what separates an agent that helps from one that guesses.
Permission and oversharing remediation in SharePoint first, then a scoped pilot with a measured baseline, role-based enablement for finance, legal and operations, and an honest 90-day review of who should keep a seat. The deliverable is adoption evidence, not a training deck.
A governed lakehouse on OneLake with a certified Power BI semantic model and row-level security, so the board pack and the regulator's return come from the same tested numbers — and the audit trail is a query rather than a folder of spreadsheets.
Foundry agents extracting structured fields from FICA packs, claim forms and supplier invoices, with personal information classified and masked before a model sees it, and a human approval step wherever the output moves money.
Copilot Studio voice agents with consent-based recording, hold and resume, and clean handoff to a human with context preserved — connected to the CRM so the agent can actually resolve rather than only deflect.
Computer use agents driving legacy line-of-business applications on a Windows 365 cloud PC, with session replay and audit logging, for the estates where an integration project would cost more than the process is worth.
Entra Agent ID, an Agent 365 inventory and DLP scoped per agent, with Copilot credit forecasting — put in place while you have five agents, because the organisations that wait until forty spend the next quarter doing archaeology.
What we're building, testing and shipping on Microsoft — written up as we go.
A practical guide to Microsoft 365 Copilot implementation for South African organisations — including the data residency question most vendor pages quietly skip.
Read6 minChoosing the right copilot platform in 2026 for your South African business is critical. We compare Claude Cowork and Microsoft Copilot to help you decide.
Read7 minComparing Claude Co-Work vs. Copilot for South African businesses in 2026. We break down the differences in agentic capabilities and integration for…
Read7 minCopilot Cowork is Microsoft 365's multi-agent workspace from Wave 3. What it does, how it compares to Claude Cowork and Gemini Enterprise, and how to govern it.
Read8 minTell us what you're trying to achieve and we'll map the right approach on Microsoft — no obligation.
Book a free AI assessmentMicrosoft and the Microsoft logo are trademarks of Microsoft Corporation. Automation Architects is an independent consultancy and is not affiliated with, sponsored by, or endorsed by Microsoft Corporation. References to Microsoft describe the technologies we implement and do not imply certification of any specific outcome.