Power BI — customer portal or Microsoft-certified distribution

Current package: DataAI Spark JARs and Microsoft deployment documentation in a ZIP.
Boundary: no DataAI .mez connector, custom visual, or installable Power BI app is included.
The current ZIP is not directly eligible as a Power BI app offer. The customer-portal route is ready for controlled JAR fulfillment. A Microsoft Marketplace/AppSource route first requires a real supported Microsoft offer artifact, appropriate installation URL, Partner Center onboarding, and certification.

1. Approve the Power BI architecture

  1. Document the Spark or Databricks environment where DataAI runs, the governed output tables it publishes, and the native Power BI connection used to read those outputs.
  2. Confirm Power BI tenant, capacity, gateway/network path, data-source credentials, refresh ownership, row-level security, privacy levels, and production support responsibilities.
  3. Verify the Yanbor commercial agreement/order covers the customer, DataAI version, Spark environments, and Power BI consumption.
  4. Do not describe the current package as a Power BI connector, visual, template app, transactable Microsoft offer, or Microsoft-certified product.

2A. Fulfill the DataAI libraries through the customer portal

  1. Obtain DataAIETL-Microsoft-1.0.0.zip, the Spark production package when required, and ARTIFACTS.sha256.
  2. Recompute SHA-256 values and validate the packages on a clean compatible Spark runtime.
  3. Create an authenticated customer entitlement and upload only the approved immutable files to its production download area.
  4. Set customer, version, environments, authorized contacts, entitlement dates, commercial reference, and support owner. Do not expose a public static download.
  5. Test the exact customer download path, checksum verification, Spark installation, DataAI output generation, and Power BI native connection to the approved output.
  6. Give the customer the portal link, filenames/hashes, entitlement reference, Spark and Power BI installation/usage guides, supported runtime baseline, output contract, and support path.
  7. Record acceptance and revoke access when commercial authorization ends.

2B. Create a Microsoft-certified distribution path

  1. Choose the Microsoft offer type that matches an artifact DataAI actually supplies. For a Power BI app offer, build and validate a real installable Power BI app and obtain its Power BI app installation URL. Do not use the Spark ZIP as the app package.
  2. Complete Microsoft AI Cloud Partner Program and Partner Center marketplace enrollment for Yanbor LLC, including publisher profile, agreements, tax/payout data where required, support contact, and company verification.
  3. Prepare the offer's legal terms, privacy policy, support URL, documentation, logos, screenshots, categories, industries, search terms, descriptions, availability, lead destination, and Power BI installation URL.
  4. Keep the promise precise: the Power BI artifact visualizes governed outputs produced by separately installed DataAI ETL Spark libraries. List Java, Spark, platform, gateway, and commercial-license prerequisites prominently.
  5. In Partner Center, create a new commercial marketplace offer of the approved type and complete Offer setup, Properties, Availability, Technical configuration, and Marketplace listing.
  6. For a Power BI app offer, use the valid app installation link supplied by Power BI. Follow Microsoft's current pricing/fulfillment rules; Power BI app offers may use publisher-managed licensing rather than direct Marketplace software fulfillment.
  7. Preview the offer and test all links and install steps with a clean authorized tenant. Ensure the listing never exposes proprietary JARs without Yanbor authorization.
  8. Select Review and publish, fix validation or certification issues, and submit. Keep the listing non-public until both Microsoft certification and Yanbor release approval are complete.
  9. After Microsoft publishes it, verify the live page, acquisition/install flow, documentation, customer-entitlement handoff, and support path. Only then label that exact offer Microsoft-certified.

3. Release and support controls

Official references

Back to DataAI ETL Markets