[Launched] Generally Available: Oracle schema conversion to Azure PostgreSQL in Visual Studio Code
What the source says
You can now convert Oracle database schema objects to Azure Database for PostgreSQL-compatible schema directly in the PostgreSQL extension for Visual Studio Code. The experience provides a project-based workflow for Oracle to Microsoft for PostgreSQL offerings, using Azure Database for PostgreSQL flexible server as a scratch database for validation and testing during schema conversion. The workflow automatically flags items that can't be converted as Review Tasks, so you can address them before applying the generated artifacts. With this release, you can move schema conversion into a guided Visual Studio Code experience instead of managing the process across separate tools. You can load Oracle schemas, run conversion, validate converted objects, review flagged items, and then apply the generated PostgreSQL artifacts with more visibility into what was converted and what still needs attention. Learn more .
Why it matters: The workflow automatically flags items that can't be converted as Review Tasks, so you can address them before applying the generated artifacts.
Urgency: Monitor
Next action: Discuss whether the customer has Oracle schemas that need conversion to Azure Database for PostgreSQL-compatible schema.
Commercial opportunities
Explore adoption of the PostgreSQL extension for Visual Studio Code for Oracle-to-PostgreSQL schema conversion.
Technical actions
Validate the guided workflow with a representative Oracle schema and review the generated Review Tasks before applying artifacts.
Questions to ask the customer
Are you currently managing Oracle-to-PostgreSQL schema conversion across separate tools?
Which converted objects require validation before PostgreSQL artifacts are applied?
Risks and objections
Items that can't be converted still require review before the generated artifacts are applied.
Points to confirm
The effective date is unknown.
The affected scope is unknown.
Reading for it_manager_dsi
Who is affected: Oracle database schema objects and items that can't be converted
Why it matters: The workflow automatically flags items that can't be converted as Review Tasks before applying the generated artifacts.
Urgency: Monitor
Next action: Evaluate the guided Visual Studio Code workflow for an Oracle schema conversion pilot.
Commercial opportunities
Assess whether this workflow supports a broader Oracle to Microsoft for PostgreSQL migration initiative.
Technical actions
Load representative Oracle schemas, run conversion, validate converted objects, review flagged items, and inspect the generated PostgreSQL artifacts.
Questions to ask the customer
Which Oracle schemas should be used for validation and testing?
How many conversion items are expected to require Review Tasks?
Risks and objections
Conversion coverage and the number of items requiring manual review are not specified in the source.
Points to confirm
The effective date is unknown, so timing for adoption is unclear.
The affected scope is unknown; the source does not specify which teams, environments, or schemas are included.
Reading for partner_channel
Who is affected: Oracle to Microsoft for PostgreSQL offerings
Why it matters: The guided Visual Studio Code experience provides more visibility into what was converted and what still needs attention.
Urgency: Monitor
Next action: Assess partner readiness to support Oracle schema conversion through the PostgreSQL extension for Visual Studio Code.
Commercial opportunities
Explore partner-led migration and schema-conversion services for Oracle to Azure Database for PostgreSQL projects.
Technical actions
Test the project-based workflow, validation process, Review Tasks, and application of generated PostgreSQL artifacts.
Questions to ask the customer
Are you currently evaluating or executing Oracle to Azure Database for PostgreSQL schema conversions?
Which schema objects require validation or review before applying generated PostgreSQL artifacts?
Risks and objections
Some items may not convert automatically and may require attention as Review Tasks.
Points to confirm
The effective date is unknown.
The affected scope is unknown.
Reading for sales_manager
Who is affected: Oracle to Microsoft for PostgreSQL offerings
Why it matters: The guided Visual Studio Code experience provides more visibility into what was converted and what still needs attention.
Urgency: Monitor
Next action: Identify accounts evaluating Oracle-to-PostgreSQL migration and assess whether this generally available workflow is relevant.
Commercial opportunities
Discuss migration-assessment conversations with accounts where Oracle schema conversion is being considered.
Technical actions
Validate the workflow with representative Oracle schemas, including review of automatically flagged Review Tasks.
Questions to ask the customer
Are you evaluating Oracle-to-PostgreSQL schema conversion, and would a guided Visual Studio Code workflow be relevant to that evaluation?
Risks and objections
Some schema objects may require manual review because the workflow automatically flags items that can't be converted.
Points to confirm
The effective date is unknown.
The affected account and workload scope are unknown.
Evidence and traceability
Each excerpt is linked to the primary source. Current raw version: 258.
Raw capture : 2026-08-26T14:18:57.653130+00:00 — hash 75e1130367433989…
Event
[Launched] Generally Available: Oracle schema conversion to Azure PostgreSQL in Visual Studio Code You can now convert Oracle database schema objects to Azure Database for PostgreSQL-compatible schema directly in the PostgreSQL extension for Visual Studio Code. The experience provides a project-based workflow for Oracle to Microsoft for PostgreSQL offerings, using Azure Database for PostgreSQL flexible server as a scratch database for validation and testing during schema conversion. The workflow automatically flags items that can't be converted as Review Tasks, so you can address them before applying the generated artifacts. With this release, you can move schema conversion into a guided Visual Studio Code experience instead of managing the process across separate tools. You can load Oracle schemas, run conversion, validate converted objects, review flagged items, and then apply the generated PostgreSQL artifacts with more visibility into what was converted and what still needs attention. Learn more .
[Launched] Generally Available: Oracle schema conversion to Azure PostgreSQL in Visual Studio Code You can now convert Oracle database schema objects to Azure Database for PostgreSQL-compatible schema directly in the PostgreSQL extension for Visual Studio Code. The experience provides a project-based workflow for Oracle to Microsoft for PostgreSQL offerings, using Azure Database for PostgreSQL flexible server as a scratch database for validation and testing during schema conversion. The workflow automatically flags items that can't be converted as Review Tasks, so you can address them before applying the generated artifacts. With this release, you can move schema conversion into a guided Visual Studio Code experience instead of managing the process across separate tools. You can load Oracle schemas, run conversion, validate converted objects, review flagged items, and then apply the generated PostgreSQL artifacts with more visibility into what was converted and what still needs attention. Learn more .
You can now convert Oracle database schema objects to Azure Database for PostgreSQL-compatible schema directly in the PostgreSQL extension for Visual Studio Code.
The experience provides a project-based workflow for Oracle to Microsoft for PostgreSQL offerings, using Azure Database for PostgreSQL flexible server as a scratch database for validation and testing during schema conversion.
You can now convert Oracle database schema objects to Azure Database for PostgreSQL-compatible schema directly in the PostgreSQL extension for Visual Studio Code.
The experience provides a project-based workflow for Oracle to Microsoft for PostgreSQL offerings, using Azure Database for PostgreSQL flexible server as a scratch database for validation and testing during schema conversion.
[Launched] Generally Available: Oracle schema conversion to Azure PostgreSQL in Visual Studio Code You can now convert Oracle database schema objects to Azure Database for PostgreSQL-compatible schema directly in the PostgreSQL extension for Visual Studio Code. The experience provides a project-based workflow for Oracle to Microsoft for PostgreSQL offerings, using Azure Database for PostgreSQL flexible server as a scratch database for validation and testing during schema conversion. The workflow automatically flags items that can't be converted as Review Tasks, so you can address them before applying the generated artifacts. With this release, you can move schema conversion into a guided Visual Studio Code experience instead of managing the process across separate tools. You can load Oracle schemas, run conversion, validate converted objects, review flagged items, and then apply the generated PostgreSQL artifacts with more visibility into what was converted and what still needs attention. Learn more .
You can now convert Oracle database schema objects to Azure Database for PostgreSQL-compatible schema directly in the PostgreSQL extension for Visual Studio Code.
The experience provides a project-based workflow for Oracle to Microsoft for PostgreSQL offerings, using Azure Database for PostgreSQL flexible server as a scratch database for validation and testing during schema conversion.