𝐂𝐨𝐫𝐞 𝐭𝐨𝐩𝐢𝐜 : 𝐝𝐚𝐭𝐚 𝐬𝐨𝐮𝐫𝐜𝐞𝐬 𝐬𝐞𝐜𝐮𝐫𝐢𝐭𝐲 Push integration to the maximum by creating on domains areas (spaces ?) , "ready to use" and "multi artifacts usage" external sources connections

Push integration to the maximum by creating on domains areas (spaces ?) , "ready to use" and "multi artifacts usage" external sources connections

✔️ Avoid to share ERP & API & cloud & on premise & folders credentials to several E.T.L items creators

✔️ Why to share my SAP credentials with 20 data engineer , despite fortunately they are Fabric cross Workspaces SQL tables shortcuts to reduce exposure ?

✔️ "Sanctify" settings on a RESTRICTED area by DOMAINS (decorrelate from ingestion tools themselves)

✔️ Use logical names

✔️ Persona could be a domain data sources manager

✔️ Prepare data sources settings (credentials , token , secretes , managed access , keyvault secrets access) for LARGE builders audience

✔️ Each data sources connections to be Key vault providers & managed compliant

✔️ Manage on premise (via the on prise gateways) & cloud data sources on the same place

✔️ "One click" usage on Data pipeline tasks , dataflow gen2 , notebooks , event stream source , power bi , data flow , azure python functions , mirroring sources etc ...

✔️ Of course , also power BI desktop needs to see shared with me datasources (domain sources hub page)

✔️ Share with consumers builders (user + ETL tool name)

✔️ Administration : Will also avoid duplicated datasource setups and give usage informations