web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Microsoft Dynamics 365 | Integration, Dataverse...
Suggested answer

PPAC_DATA INTEGRATION_REGION ERROR

(3) ShareShare
ReportReport
Posted on by
Dear Sir,
 
We got an error message in PPAC.
 
We made the production environment in West_US as follow;
 
After that, we automatically got an PPAC region as United States. 
 
 
By the way we click 'Data integration' that the error message appeared. 'Region is not supported'
 
 
Is there anyone to solve this problem. Please let me know.
 
Also which one did we do incorrect action when we made the environment?
 
We already issued the MS ticket and they are checking the issue.
But they said just new creating Reproduction.
Is it good solution? Is there any other solution?
 
Please check and let me know.
 
Thanks
 
Best regards
HY
I have the same question (0)
  • Suggested answer
    DAnny3211 Profile Picture
    Moderator on at
    PPAC_DATA INTEGRATION_REGION ERROR

    Hi HY,

    Thanks for sharing the detailed breakdown of your issue. Based on the information across all three parts, it seems the error you're encountering—“Region is not supported”—is related to a mismatch between the Power Platform Admin Center (PPAC) region and the Finance and Operations (F&O) environment region.

    Here's what might be happening and what you can do:

    1. Region Mismatch

    Even though your environment was created in West US, the PPAC region is showing as United States, which may not be fully aligned with the backend services required for Data Integration. This mismatch can cause the "Region is not supported" error when accessing certain features.

    2. Data Integration Region Requirements

    The Data Integration feature has specific region support requirements. If the PPAC region doesn’t match the supported regions for Data Integration, the feature may not work—even if the environment itself is valid.

    3. Reproduction Environment

    Creating a new reproduction environment, as suggested by Microsoft Support, is a valid troubleshooting step. It helps isolate whether the issue is with the specific environment setup or a broader regional limitation.

    4. Alternative Solutions

    • Check Region Compatibility: Review Microsoft’s documentation on supported regions for Data Integration and PPAC features.
    • Use a Different Region: If possible, try creating a new environment in a region explicitly listed as supported for Data Integration.
    • Wait for Microsoft’s Response: Since you’ve already opened a support ticket, they may be able to escalate the issue or provide a backend fix.

    Let me know if you'd like help checking region compatibility or setting up a test environment.

    If this answer was helpful, please consider marking it as accepted.
    Best regards,
    Daniele

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Mansi Soni – Community Spotlight

We are honored to recognize Mansi Soni as our August 2025 Community…

Announcing our 2025 Season 2 Super Users!

A new season of Super Users has arrived, and we are so grateful for…

Congratulations to the July Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Microsoft Dynamics 365 | Integration, Dataverse, and general topics

#1
Amitsb1980 Profile Picture

Amitsb1980 17

#1
CU06061003-0 Profile Picture

CU06061003-0 17

#1
LR-09071359-0 Profile Picture

LR-09071359-0 17

Product updates

Dynamics 365 release plans