unified project structure for hacks#267
Merged
MSFT-LarsFisch merged 72 commits intomicrosoft:mainfrom Feb 18, 2026
Merged
Conversation
- Changed title from "Regional Protection and Disaster Recovery (DR)" to "Regional Protection (Backup)" - Removed disaster recovery/site recovery content (moved to challenge-04) - Updated goal to focus solely on backup and restore operations - Replaced datacenter/AZ diagram with Azure VM backup architecture diagram - Removed Challenge 3.2 (DR within Azure Region) - relocated to separate challenge - Clarified VM restore wording from "to Azure" to "on Azure" - Added optional blob storage restore task - Updated success criteria to align with backup-only scope - Consolidated learning resources and fixed broken link formatting - Fixed navigation links to use "Challenge" instead of "Challenge Solution" These changes address feedback about unclear goals and terminology inconsistencies between backup and DR concepts.
- Changed title from "Protect in Azure with Disaster Recovery (Inter-regional)" to "Regional Disaster Recovery (DR)" - Updated goal to focus on intra-region DR across Availability Zones instead of inter-region DR - Removed cross-region failover tasks (Germany West Central to Sweden Central) - Added new architecture diagram showing zone-to-zone disaster recovery - Simplified tasks to focus on: 1. Setting up DR for Linux VM within primary region 2. Simulating zone-to-zone failover - Updated success criteria to reflect zone-to-zone DR scope - Replaced inter-region learning resources with zone-to-zone specific documentation - Fixed navigation links to use "Challenge" instead of "Challenge Solution" These changes address feedback about unclear goals and separate zone-level DR from region-level DR concepts.
- Changed title from "Protect your Azure PaaS with Disaster Recovery" to "Disaster Recovery (DR) across Azure Regions" - Removed Azure Storage Account DR tasks (moved to separate challenge or optional content) - Removed Challenge 1 & 2 (Composite SLA calculations with Copilot) - Removed Challenge 3 (Storage Account DR) - Updated goal to focus on cross-region VM protection using Azure Site Recovery - Specified concrete regions: Germany West Central (primary) to Sweden Central (secondary) - Identified specific VMs to protect (*-web1 and *-web2) - Added new architecture diagram for cross-region ASR - Streamlined tasks to focus on: 1. Setting up and monitoring ASR replication 2. DR drill with test failover 3. Production failover and failback - Updated success criteria to align with cross-region VM failover scope - Replaced storage-focused learning resources with ASR-specific documentation - Fixed navigation links to use "Challenge" instead of "Challenge Solution" These changes address feedback about confusing challenge structure and clarify the distinction between zone-level and region-level DR.
Simplified Challenge 5 to focus solely on cross-region disaster recovery operations without failback complexity: - Removed references to failback from goal and task descriptions - Updated Task 3 to end at production failover instead of including failback - Removed failback from success criteria - Streamlined challenge to focus on: ASR setup, test failover, and production failover to secondary region (Germany West Central → Sweden Central) This change separates failback operations into a dedicated challenge (06/07), making the learning progression clearer and reducing cognitive load for participants learning cross-region DR concepts.
…er reconnection Completely restructured Challenge 6 to focus on post-failover operations and storage account disaster recovery: Changes: - Changed from "Failback to Primary Region" to "Protect your Azure PaaS with DR" - Added Task 1: Re-establish web application connectivity in secondary region - Reconnect failed-over VMs to load balancer backend pool in Sweden Central - Test application accessibility from secondary region - Added Task 2: Storage Account GRS verification and testing - Verify GRS configuration and identify paired region - Perform storage account failover test - Updated success criteria to reflect PaaS DR focus instead of VM failback - Simplified learning resources to focus on storage redundancy and DR This change creates a logical progression: Challenge 5 performs failover, Challenge 6 validates the DR environment and tests PaaS services, preparing for eventual failback in Challenge 7.
…d challenge Restructured Challenge 7 from monitoring/SQL focus to comprehensive failback: Changes: - Removed "Extra Challenge" designation and Application 2 content - Changed from "Monitor & Protect PaaS (SQL)" to "Failback to Primary Region" - Removed Application Insights monitoring tasks (azd monitor) - Removed Azure SQL Database failover group tasks - Added comprehensive failback workflow: - VM failback from Sweden Central → Germany West Central - Re-protection of VMs for DR back to secondary region - Traffic Manager endpoint verification - Storage Account failback - Data integrity validation - Enhanced success criteria with detailed validation points for failback - Updated learning resources to focus on ASR reprotection and failback This creates a complete DR lifecycle: Challenge 5 (failover) → Challenge 6 (validate DR environment) → Challenge 7 (failback to primary). The workshop now provides end-to-end cross-region DR experience.
Changed storage account SKU from Standard_LRS to Standard_GRS to enable geo-redundant storage for disaster recovery capabilities: Files modified: - 03-Azure/01-03-Infrastructure/04_BCDR_Azure_Native/Infra/App1/MODULES/STORAGE/storage.bicep - 03-Azure/01-03-Infrastructure/04_BCDR_Azure_Native/Infra/App1/deploy.json Changes: - Updated storage account SKU: Standard_LRS → Standard_GRS - Enables automatic asynchronous replication to paired Azure region - Provides cross-region data durability and availability - Supports Challenge 6 storage account failover testing requirements With GRS enabled, the storage account data is now replicated to the paired region, allowing participants to perform storage account disaster recovery testing and failover operations as part of the BCDR workshop.
Fixed inconsistent navigation links and challenge numbering across challenge files: - challenge-01.md: Changed "Next Challenge Solution" → "Next Challenge" - challenge-02.md: Changed "Previous/Next Challenge Solution" → "Previous/Next Challenge" - challenge-04.md: Fixed broken next challenge link (challenge-04.md → challenge-05.md) - challenge-07.md: Changed "Previous Challenge Solution" → "Previous Challenge" These changes ensure consistent navigation terminology throughout the workshop and fix the circular reference in challenge-04 where it pointed to itself instead of challenge-05.
Created a setup bash script for the BCDR Lab
Feature/bcdr workshop improvements
Member
Author
|
@nilsbankert can you review this? happy to jump into a teams call with you, in case you require more information. |
MSFT-LarsFisch
approved these changes
Feb 18, 2026
Collaborator
MSFT-LarsFisch
left a comment
MSFT-LarsFisch
left a comment
There was a problem hiding this comment.
enable unified structure for hackbox console
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
introducing a similar structure to what the hack