Architecture design
Account, network and identity structure (landing zone) with multi-zone redundancy as the default.
- Azure landing zones
- Management groups · Subscriptions
- Virtual Network · Azure Firewall
- Azure Well-Architected Framework
Cloud MSP · Microsoft Azure
A standardized Azure estate, with databases run right
Governance with Azure landing zones and Azure Policy, and PostgreSQL and MySQL flexible servers run by database specialists.
Reference architecture
Reference architecture on Microsoft Azure
Policies applied by management group and subscription; the data tier considers zone-redundant HA and geo-restore.
Management groupsAzure Policy
Microsoft Entra IDRBAC · PIM
Identity & network boundary
Application GatewayWAF · Front Door
VM · AKS · App ServiceAvailability zones
Application → data tier
Flexible serverzone-redundant HA
Read replicaread scale
Backup · DRAzure Backup · Site Recovery
Azure Monitor · Defender for CloudCost Management · AdvisorTerraform / Bicep pipeline
- Management-group hierarchy with Azure Policy guardrails
- Least privilege with Microsoft Entra ID RBAC and PIM
- HA, read replicas and maintenance windows for flexible server
- Infrastructure and database logs unified in Azure Monitor and Log Analytics
MSP scope
MSP scope on Microsoft Azure
Representative services we use in each area, adjusted to your environment and contract scope.
Migration to cloud
Step-by-step moves, from server rehosting to managed database replatforming.
- Azure Migrate
- Azure Database Migration Service
- Migration service in Azure Database for PostgreSQL
- Azure Data Box
24x7 monitoring & operations
Metrics, logs and events collected and run through incident and change processes.
- Azure Monitor · Log Analytics
- Azure Service Health
- Azure Update Manager
- Azure Automation
Cost optimization (FinOps)
Visibility, budget alerts, right-sizing and commitment reviews on a recurring cycle.
- Microsoft Cost Management
- Azure Advisor
- Azure Reservations
- Azure savings plan for compute
Security & compliance
Least privilege, encryption, audit logging and security-recommendation reviews by default.
- Microsoft Entra ID
- Microsoft Defender for Cloud
- Azure Policy
- Azure Key Vault · Microsoft Sentinel
Backup & DR
Backup policies and recovery objectives (RPO/RTO), proven by restore drills.
- Azure Backup
- Azure Site Recovery
- Geo-redundant storage (GRS)
- Geo-restore · read replicas
Managed database operations
DBA-level care for parameters, performance and the version lifecycle of managed databases.
- Azure Database for PostgreSQL flexible server
- Azure Database for MySQL flexible server
- Query Store · Query Performance Insight
- MariaDB → VM or MySQL flexible server
IaC & automation
Infrastructure as code, with deployments and routine checks automated in pipelines.
- Terraform
- Bicep
- ARM templates
- Azure DevOps · GitHub Actions
Managed databases
Choosing a managed database on Microsoft Azure
For each open-source engine: the managed service available on this cloud, or the self-managed alternative.
| Engine | Managed service / alternative | Notes |
|---|---|---|
| MySQL | Azure Database for MySQL flexible server | Managed service available — we manage parameters, performance and upgrade plans |
| PostgreSQL | Azure Database for PostgreSQL flexible server | Managed service available — we manage parameters, performance and upgrade plans |
| MariaDB | Azure VM (self-managed) / migrate to MySQL flexible server | Azure Database for MariaDB was retired on 2025-09-19 — move to MySQL flexible server or run on VMs |
| InfluxDB | Azure VM · AKS (self-managed) | No managed service — self-managed on VMs/containers (linked to our open-source DB services) |
| Oracle · SQL Server | Azure SQL / VM; Oracle → PostgreSQL via ora2pg | Usually the source of a heterogeneous migration — see Data Migration |
Azure Database for MariaDB was retired on 19 September 2025. Existing MariaDB workloads either move to Azure Database for MySQL flexible server (after a compatibility review) or run self-managed on VMs.
Migration to cloud
Migrating to Microsoft Azure
Assess
Inventory servers and databases, map dependencies, baseline performance, review licensing and choose rehost, replatform or refactor.
Landing zone
Build account, network, identity and logging standards first, as code.
Migrate
We start from Azure Migrate for servers and Azure DMS (MySQL) · Migration service in Azure Database for PostgreSQL for databases, with ora2pg · Oracle schema conversion (VS Code PostgreSQL extension) for schema conversion.
Validate & cut over
Verify data consistency and performance, switch over against agreed criteria and keep a rollback path.
Stabilize & optimize
Heightened monitoring during hypercare, then cost and performance optimization as routine operations.
Security & compliance
Korean regulatory & security considerations
- Region: Korea Central · Korea South — document where data and backup copies are stored
- Access control, encryption and access-log retention designed with the Personal Information Protection Act and ISMS-P in mind
- Public sector: confirm whether CSAP (Cloud Security Assurance Program) applies and which certification scope is required
- Operating procedures that keep audit logs, change history and access reviews as evidence
These are general considerations. OpenDB Works does not act as a certification agent or guarantee certification; interpretation of requirements rests with your security team and the certification body.
FAQ
Frequently asked questions
Can Azure DMS migrate Oracle to PostgreSQL?
No. Azure DMS does not support Oracle → PostgreSQL. Following Microsoft guidance we use ora2pg or the Oracle schema conversion in the PostgreSQL extension for VS Code, and design data movement separately.
Which tool do you use for PostgreSQL migrations?
We first consider the Migration service in Azure Database for PostgreSQL (online/offline), and use pg_dump/pg_restore or logical replication where requirements call for it.
Are you a Microsoft partner?
We do not publish partner designations or certifications on this site; we can share them during consultation if relevant.
Shall we start by reviewing your cloud and databases as they are today?
Tell us your clouds, database versions, topology and concerns, and we will propose an assessment scope and approach.