2BIT AG
Section III
Publish Workload Requirements Attestation Checklist
We, the vendor, 2BIT AG, confirm and attest to reviewing, meeting, and complying with the requirements outlined in the Microsoft Fabric Workload Development Kit (WDK), specifically the Publish Workload Requirements located at https://learn.microsoft.com/en-us/fabric/workload-development-kit/publish-workload-requirements .
The following sections document details, exceptions, or variances regarding the attestation of adherence to the Publish Workload Requirements.
Business Requirements:
1. Value To Customers: The workload provides the following value to customers
[X] Yes[ ] No
Secure, scalable dbt transformations in Microsoft Fabric.
2. Trial: We provide an easy and fast trial experience (< 5 seconds), enabling users to explore the workload.
[X] Yes[ ] No
3. Monetization: Monetization experience available.
[ ] Yes[X] No
Planned for the next release.
4. Terms and Conditions: Published and highlight compliance aspects of the solution.
[ ] Yes[ ] No
Link: [REPLACE: https://your-domain/terms]
5. Metadata: Title, summary, and icon identical between workload manifest and SaaS offer.
[ ] Yes[ ] No
6. Attestation Document: Link is added to the workload metadata manifest (supportLink) and shown on the product page.
[ ] Yes[ ] No
Link: this page URL.
7. Marketplace Offer: SaaS offer listed in Azure Marketplace (can be “Contact us”).
[ ] Yes[ ] No
Link: [REPLACE: Azure Marketplace listing URL]
8. Documentation: Customer documentation available and easy to understand.
[ ] Yes[ ] No
Link: [REPLACE: docs URL]
Technical Requirements:
1. Microsoft Entra Access: Only Microsoft Entra authentication/authorization is used.
[X] No additional authentication and authorization mechanisms are used
[ ] Additional authentication and authorization mechanisms are used for stored data in Fabric
2. OneLake: Workloads integrate with OneLake to store data in platform-supported formats.
[ ] All data and metadata is stored in OneLake or Fabric Data Stores
[X] Not all data and metadata is stored in OneLake or Fabric Data Stores
Partial integration; not all data stored in OneLake.
3. Microsoft Entra Conditional Access: Service works fully when customers enable this.
[X] The service works in its entirety even if customers enable this functionality
[ ] The service works with limitations if customers enable this functionality
[ ] The service does not work with Microsoft Entra Conditional Access
4. Admin REST API: Microsoft Fabric Admin APIs are leveraged (/admin/*).
[X] Microsoft Fabric Admin API’s are being leveraged (/admin/*)
[ ] No Microsoft Fabric Admin API’s are being used
5. Customer-Facing Monitoring & Diagnostic: Health/telemetry data stored for ≥ 30 days.
[X] Minimum 30 days requirement is adhered to
[ ] Vendor stores the data for additional days beyond the minimum requirement
6. B2B: Cross-tenant collaboration supported.
[ ] Cross tenant B2B collaboration supported
[X] Workload Item Access only within the tenant
7. Business Continuity and Disaster Recovery (BCDR): BC/DR strategy documented.
[ ] BC/DR strategy is available
[X] BC/DR handled by the customer’s Fabric environment
8. Performance: Metrics available via Monitoring Hub.
[X] Performance Metrics on workload performance are available via Monitoring Hub
[ ] Performance tracking is not currently available to end users
9. Presence: Service availability and regional alignment declared.
[X] Service availability and colocation/alignment in the following Fabric regions
[ ] All or part of the service does not reside in Azure
Hosted in Switzerland region.
10. Public APIs: Public Microsoft Fabric APIs are used.
[X] Yes[ ] No
Design / UX Requirements:
1. Common UX: Complies with Fabric UX guidelines.
[X] No exceptions have been granted by Microsoft
[ ] The following variance and/or exceptions have been granted by Microsoft
2. Item Creation Experience: Complies with Fabric UX System.
[X] Yes[ ] No
3. Monitoring Hub: Long running operations integrate with Monitoring Hub.
[X] Yes[ ] No
4. Trial Experience: Provided as outlined in the design guidelines.
[X] Trial Supported[ ] Trial Not Supported
5. Monetization Experience: Follows Fabric Templates.
[ ] Supported now[X] Planned
6. Accessibility: Fully compliant with Fabric UX accessibility guidelines.
[X] The user experience is completely compliant with the guidelines
[ ] The following limitations exist
7. World Readiness / Internationalization:
[ ] English is the only supported language
[X] The following are the additional languages supported
German.
8. Jobs To Be Done: Onboarded to the JTBD definition for Item types.
[ ] Yes[ ] No
9. Item Settings: Implemented in the ribbon.
[X] Yes[ ] No
10. Samples: Provided to help customers get started.
[X] Sample provided[ ] Samples not provided
11. Custom Actions:
[X] Custom Actions are not implemented[ ] Custom Actions implemented
12. Workspace settings:
[ ] Supported[X] Not Supported
13. Global Search:
[ ] Supported[X] Not supported
Security / Compliance Requirements:
1. Security general: Workloads undergo security assessment/review.
[ ] Confirmed[ ] Not Confirmed
[OPTIONAL NOTE: Add SAST/DAST/pen-test notes if applicable]
2. Privacy: Privacy assessment and review performed. Cookies usage complies with Fabric rules.
[X] Partner workloads aren’t to use, write, or rely on third-party cookies
[X] Workload owners only use essential HTTP-only, same-origin cookies after positive authentication
2BIT AG: No cookies used; privacy review complete.
3. Data Residency: Data remains local to the customer tenant/geography.
[X] Yes[ ] No
Fully local to customer tenant; hosted presence in Switzerland.
Support:
1. Live site contact details and support channels provided.
[X] Yes[ ] No
Contact Name/Team: 2BIT Support
Email: support@2bit.ch
Contact Form: /contactus
2. Supportability: SLA/contact methods published and accessible from the workload.
[X] We confirm that support information is published and directly accessible to users
3. Service Health and Availability: Status page published.
[ ] Yes[X] No
Dashboard coming soon.
Fabric Features:
1. Application Life Cycle Management (ALM)
[ ] Supported[X] Not Supported
2. Private Links
[ ] Supported[X] Not Supported
3. Data Hub
[ ] Supported[X] Not Supported
4. Data Lineage
[ ] Supported[X] Not Supported
5. Sensitivity labels
[ ] Supported[X] Not Supported
Extra requirements (if implementing Export functionality)
[ ] The export functionality has been implemented in accordance with the guidelines
[X] No export functionality is provided