Prototype in Sandbox → Build and experiment
This is where we can test ideas, create educational materials, and build PoC projects
USA / Costa Rica
Last updated: 2026-04-08
Important
This is about different topics and areas within Microsoft Cloud Technologies. The Microsoft Cloud
ecosystem includes a range of products and solutions designed to work together to provide comprehensive
cloud services. It was created to have a hub with demos, technical talks, solutions, use cases, etc.,
about Microsoft Cloud and to share personal experience and learning with the community.
The information provided and any document (such as scripts, sample codes, etc.) is provided AS-IS and WITH ALL FAULTS. Pricing estimates are for demonstration purposes only and do not reflect final pricing. Microsoft assumes no liability for your use of this information and makes no guarantees or warranties, expressed or implied, regarding its accuracy or completeness, including any pricing details. Please note that these demos are intended as a guide and are based on personal experiences. For official guidance, support, or more detailed information, please refer to Microsoft's official documentation or contact Microsoft directly: Microsoft Sales and Support
Endorsed for: (Click to expand)
Certifications: (Click to expand)
Copilot services and tools:
flowchart LR
subgraph Personal_Productivity[Personal Productivity]
CopilotChat[Copilot Chat] --> M365Copilot[M365 Copilot]
end
subgraph Business_Productivity[Business Productivity]
MicrosoftAgents[Microsoft Agents]
end
subgraph Extensibility[Extensibility]
CopilotStudio[Copilot Studio] --> AzureAIFoundry[Azure AI Foundry]
end
subgraph Customizability[Customizability]
ThirdPartyCustomAgents[3rd Party & Custom Agents]
end
M365Copilot --> MicrosoftAgents
MicrosoftAgents --> CopilotStudio
AzureAIFoundry --> ThirdPartyCustomAgents
Deployment lifecycle of software:
flowchart LR
subgraph Versioning[Semantic Versioning]
Major[Major Version: X] --> Minor[Minor Version: X.X]
Minor --> Patch[Patch Version: X.X.X]
end
subgraph Release_Types[Release Types]
DevBuild[Development Build] --> Alpha[Alpha Release]
Alpha --> Beta[Beta Release]
Beta --> RC[Release Candidate]
RC --> Stable[Stable Release]
end
subgraph Maintenance[Maintenance & Updates]
Stable --> Hotfix[Hotfix Patch]
Stable --> FeatureUpdate[Feature Update Minor]
Stable --> BreakingChange[Breaking Change Major]
end
Major --> Minor
Minor --> Patch
Stable --> Versioning
Details: (Click to expand)
- Semantic Versioning (vX.X.X)
- Major (X): Introduces breaking changes. Example:
v2.0.0→ incompatible withv1.x.x. - Minor (X.X): Adds new features but remains backward-compatible. E.g:
v1.3.0. - Patch (X.X.X): Bug fixes or small improvements, no new features. E.g:
v1.3.2.
- Major (X): Introduces breaking changes. Example:
- Release Types
- Development Builds: Internal, unstable, often nightly builds.
- Alpha: Early testing, incomplete features.
- Internal testing phase.
- Features are incomplete or unstable.
- Used mainly by developers and sometimes a small internal QA team.
- Beta: Feature-complete, external testers provide feedback.
- Product is more stable and feature-complete.
- Released to a limited group of external users (beta testers).
- Goal: gather feedback, identify bugs, and test usability in real-world scenarios.
- Often comes with disclaimers: “may contain bugs,” “not final,” etc.
- Release Candidate (RC): Candidate for final release, only critical fixes allowed.
- A version that could be the final product if no major issues are found.
- Focus is on fixing critical bugs only.
- General Availability (GA): Official production-ready release.
- Official public release.
- Considered stable, supported, and ready for production use.
- Maintenance & Updates
- Hotfix (Patch): Urgent bug/security fix, increments patch number.
- Feature Update (Minor): Adds new functionality without breaking compatibility.
- Breaking Change (Major): Requires incrementing the major version due to incompatibility.
Refresh Date: 2026-04-08