![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(265.6, 75%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESL%3C/text%3E%3C/svg%3E)
1,642 questions
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(99.2, 65%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECB%3C/text%3E%3C/svg%3E)
Hi @Sovichet Ly
Thanks for the question and using MS Q&A platform.
Unfortunately, connecting to Oracle Analytics Cloud (OAC) is not supported in Microsoft Purview.
This article discusses currently supported data sources, file types, and scanning concepts in the Microsoft Purview Data Map: Supported data sources and file types.
Appreciate if you could share the feedback on our feedback channel. Which would be open for the user community to upvote & comment on. This allows our product teams to effectively prioritize your request against our existing feature backlog and gives insight into the potential impact of implementing the suggested feature.
Regarding connecting Oracle Analytics Cloud (OAC) to Microsoft Purview. As you mentioned, connecting Microsoft Purview to Oracle Analytics Cloud (OAC) can indeed be a bit complex due to the lack of a native connector.
Here is a breakdown of your connecting options and some additional information:
JDBC (Java Database Connectivity) connector (Recommended): The best practice for exploring the connecting Oracle Analytics Cloud (OAC) to Microsoft Purview is JDBC Connector approach. This is the most feasible option. OAC does offer a JDBC URL for connecting to the data within the cloud environment (https://docs.oracle.com/en/cloud/paas/analytics-cloud/acsds/connect-oracle-analytics-cloud-using-jdbc-url.html#GUID-0ED04660-58F1-4CA1-97B1-C6B8B7599BD3link that you have provided). While the Oracle Database connector in Purview isn't directly applicable, the process of using a JDBC connector for a custom solution is similar. You would need to create a custom connector to bridge Purview and OAC using JDBC. Microsoft provides a solution accelerator to help with building custom connectors (https://learn.microsoft.com/en-us/samples/microsoft/purview-custom-connector-solution-accelerator/purview-custom-connector-solution-accelerator/) link that you have provided).
Power BI Connector Explanation: Power BI has a connector for OAC, but it is not directly applicable for Purview. Power BI connectors are designed for data visualization and reporting, not for metadata management. Using the Power BI connector would require additional steps to transfer data from Power BI to Purview, which can be more complicated than using a JDBC connector.
API Connector Explanation: Using APIs to connect Purview to OAC would involve custom development work. This approach can be more complex than using a JDBC connector because it requires handling API authentication, data parsing, and integration logic. This approach might be more complicated than using a JDBC connector due to the need for extensive custom development and handling of API responses.
In summary, the JDBC connector approach seems to be the most straightforward and feasible option, although it requires some custom development work. The custom connector solution accelerator provided by Microsoft can be a valuable resource in this process.
Hope this helps. Do let us know if you any further queries.
If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.