CD Consulting R&D
CD Consulting R&D · KB-DEV · Entry 1 · slide deck · Published 9 September 2026 · Version 1
From cloud governance to the developer workstation
A guided map of Microsoft’s main portals and tools — fourteen slides, from tenant governance to the code editor.
If you have ever wondered which Microsoft portal does what, fourteen clickable slides map the whole chain.
The deck, slide by slide
1. A structured overview
Title. From cloud governance to the developer workstation: a structured overview of Microsoft’s main portals and tools — Administration, Security, Platform, Collaboration, Creation, Development. Portal: https://www.microsoft.com/
2. Overview — a four-layer journey
Map. Each portal operates at a different level while contributing to the same value chain: Govern (Admin, Entra, Azure, Power Platform admin) · Organize & share (SharePoint, Learn) · Design (Copilot Studio, Power Apps) · Deliver (Azure DevOps, GitHub, VS Code). Portal: https://www.microsoft.com/
3. Microsoft 365 Admin
Global administration. The central cockpit for managing services, users and groups, licenses and billing, service health, and global settings. Portal: https://admin.cloud.microsoft/
4. Microsoft Entra
Identity & access. The trust layer for identities, MFA and authentication, Conditional Access, applications, roles, and access governance. Portal: https://entra.microsoft.com/
5. Azure portal
Cloud infrastructure. The unified graphical console for creating, managing, and monitoring Azure resources, subscriptions and costs, with monitoring and access control. Portal: https://portal.azure.com/
6. Power Platform Admin
Low-code governance. The control center for environments, security and DLP policies, capacity and licensing, ALM and support across Power Platform. Portal: https://admin.powerplatform.microsoft.com/
7. SharePoint
Collaboration & content. The content, knowledge, and collaboration layer: sites and intranets, documents and versions, secure sharing, Teams integration. Portal: https://www.microsoft.com/microsoft-365/sharepoint/collaboration
8. Microsoft Learn
Learning. The documentation and learning gateway: product documentation, learning paths, hands-on modules, certifications. Portal: https://learn.microsoft.com/
9. Copilot Studio
AI agents & automation. A graphical low-code studio for building agents and workflows, connecting knowledge and data, and publishing to work channels. Portal: https://copilotstudio.microsoft.com/
10. Power Apps
App creation. The maker workspace for building low-code applications: canvas and templates, Dataverse, connectors, solutions and ALM. Portal: https://make.powerapps.com/
11. Azure DevOps
Delivery lifecycle. An integrated suite for planning (Boards), versioning (Repos), testing, and deployment (Pipelines, Tests & artifacts). Portal: https://dev.azure.com/
12. GitHub · Microsoft
Code collaboration. Microsoft’s collaboration space for repositories, issues and projects, pull requests, and Actions. Portal: https://github.com/microsoft
13. Visual Studio Code
Developer workstation. The free, open-source editor with integrated Git and GitHub, debugging, an integrated terminal, extensions, and AI-assisted experiences. Portal: https://code.visualstudio.com/
14. Summary — from governance to delivery
Summary. One scenario spans every layer: Entra secures, Admin governs, Azure hosts, Power Platform accelerates — secure, provide the platform, create, collaborate, deliver, and learn. Portal: https://www.microsoft.com/
Method and provenance
The deck was produced with Microsoft 365 Copilot (PowerPoint generation) on 9 September 2026, from a prompt by
CD Consulting R&D, and exported as Microsoft_Tools_Presentation_V2_Download.pptx. For this edition the
slides were converted to vector graphics (PDF then per-page SVG) after removing the fourteen decorative images that
Copilot had generated — each slide’s speaker notes credit them as “Visual on this slide was generated with Microsoft
Copilot”. The text content is reproduced as generated, unedited; the introduction and this note are by CD Consulting R&D.
Clickable areas. The buttons of the original deck are carried over: each converted slide is overlaid with transparent link areas placed at the exact position of the deck's hyperlinked shapes (geometry read from the PowerPoint file, expressed as a percentage of the slide), and the same links are repeated in text under each slide for keyboard, screen-reader and print use. Targets are those of the deck, with one substitution: the placeholder tenant address on the SharePoint slide (mysite.sharepoint.com) is replaced by Microsoft's public SharePoint page.