Fabric Attestation
November 7th, 2024 – Initial Revision
Publish Workload Requirements Attestation Checklist
We, the vendor, 42 Layers Corp, 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 documents details, exceptions, or variances regarding the attestation of adherence to the Publish Workload Requirements.
Business Requirements:
- Value To Customers: The workload provides the following value to customers –
The powerful data cleaning capabilities of the Osmos AI Data Wrangler enable organizations to produce more trustworthy insights on data managed by Fabric. Business analysts point to a folder full of files, walk away, and come back to clean data that is ready for submission to a destination table. This means Osmos users aren’t stuck trying to clean data using complex formulas, writing scripts, or doing manual cell-level cleanup.
- Trial: We provide an easy and fast trial experience. The trial is available to the customer without waiting time (less than 5 seconds), and provides a free and easy way to explore the offered workload for a limited time in accordance with Microsoft guidelines for Trials
[ ] Yes
[x] No
We will have a free tier that is restricted to the creation of one wrangler, file size limit of 5 MB. There will be a predefined limit on the number of AI tokens for data wrangling – during public preview this restriction will not be enforced.
-
Monetization: The workload is available on the marketplace for the customer to procure with or without a trial in accordance with the monetization guidelines
[x] Yes
[ ] No
The current version of the product provides a 90 day trail for all users with file sizes under 5 MB. Future versions may monetize the workload via the Azure Marketplace
Technical Requirements:
-
Microsoft Entra Access: The workload(s) use Microsoft Entra authentication and authorization.
[x] No additional authentication and authorization mechanisms are used
[ ] Additional authentication and authorization mechanisms are used for stored data In Fabric
The following is the Osmos Tenant Id 08ae9fc6-163c-4660-8eb9-c5da0a6124b2
-
One Lake: Workloads integrate with One Lake to store data in the standard formats supported by the Fabric platform so that other services can take advantage of it.
-
[x] All data and metadata is stored in One Lake or Fabric Data Stores
[ ] Not all data and metadata is store in One Lake or Fabric Data Stores
N/A
Microsoft Entra Conditional Access: Enterprise customers require centralized control and management of the identities and credentials used to access their resources and data and via Microsoft Entra to further secure their environment via conditional access.
[x] The service works in its entirety with even if customers enable this functionality
[ ] The service works in with limitations if customers enable this functionality
[ ] The service does not work Microsoft Entra Conditional Access
We fully integrate with Entra and support all of it’s access control features.
-
Admin REST API: Admin REST APIs are an integral part of Fabric admin and governance process. These APIs help Fabric admins in discovering workspaces and items, and enforcing governance such as performing access reviews, etc. Basic functionality is supported as part of the Workload Development Kit and doesn't need any work from Partners.
[ ] Microsoft Fabric Admin API’s are being leveraged (/admin/*)
[x] No Microsoft Fabric Admin API’s are being used
-
Customer Facing Monitoring & Diagnostic: Health and telemetry data needs to be stored for a minimum for 30 days including activity ID for customer support purposes, including Trials.
[x] Minimum 30 days requirement is adhered to
[ ] Vendor stores the data for __ additional days beyond the minimum requirement
-
B2B: The implementation of the workload is in line with Microsoft Fabric’s sharing strategy focused on allowing customers to collaborate with their business partners, customers, vendors, subsidiaries etc. It also means users from other tenants can potentially be granted access to items partners are creating.
[ ] Cross tenant B2B collaboration supported
[x] Workload Item Access only within the tenant
Items are not being shared across tenants, but the cleansed data / work product of the items can be shared
-
Business Continuity and disaster recovery: The vendor has a comprehensive Business Continuity and Disaster Recovery (BCDR) plans designed to tackle unplanned disasters and recovery steps.
We have a comprehensive BCDR that was verified as part of our SOC 2 compliance testing https://www.osmos.io/tos
-
Performance: The Workload implementation takes measures to test and track performance of their Items
[x] Performance Metrics on workload performance are available via the monitoring hub
[x] Workload additionally includes a separate monitoring UI to test and track performance
[ ] Performance tracking is not currently available to the end user however vendor support personnel can monitor, test, track performance via their internal instrumentation and monitoring systems
<Additional notes here>
-
Presence:To ensure that customer expectations independent of their home or capacity region are met, vendors need to align with fabric regions and clouds. Availability in certain restrictions also impacts your Data Residency commitments.
[x]Service availability and colocation/alignment in the following fabric regions
We support all regions supported by Azure with separate control and data planes in each region. Within each region we support multiple availability zones for BCD. Today that is US and EU (Frankfurt).
[x] All or part of the service does not reside in Azure
Some of our AI processing occurs on GCP infrastructure but the rest of our product runs in Azure.
-
Public APIs: Fabric Public APIs are the backbone of automation, enabling seamless communication and integration for both customers and partners within the Fabric ecosystem. Fabric Public API empowers users to build innovative solutions, enhance scalability, and streamline workflows.
[X]The workload uses Fabric Public APIs
Design / UX Requirements:
-
Common UX: The workload and all item types the partner provides as part of it comply with the Fabric UX guidelines.
[x] The workload is fully compliant with the Fabric UX guidelines
[ ] The following variance and/or exceptions have been granted by Microsoft
N/A
-
Item Creation Experience: The item creation experience is in accordance with the Fabric UX System.
[x] Yes
[ ] No
-
Monitoring Hub: All Long running operations need to integrate with Fabric Monitoring Hub.
[x] Yes
[ ] No
-
Trial Experience: The workload provides a Trial Experience for users as outlined in the design guidelines
[x] Trial Supported
[ ] Trial Not Supported
-
Monetization Experience: The monetization experience is in line with the design guidelines provided
[ ] The monetization experience is completely integrated with the market place and compliant with the guidelines
[ ] Bring Your Own License (BYOL)
[x] Free / Freemium
[ ] Other
This is a free experience during public preview. Osmos intends to monetize the workload in subsequent releases via the Azure Marketplace
-
Accessibility: The user experience is in compliance with the Fabric UX design guidelines for Accessibility
[x] The user experience is completely compliant with the guidelines
[ ] The following limitations exist
N/A
-
World Readiness / Internationalization: English is supported as the default language. Localization through optional, should be considered.
[x] English is the only supported language
[ ] The following are the additional languages supported
<List of Languages>
-
Item Settings: Itemsettings are implemented as a part of the ribbon as outlined in the UX guidelines
[x] Yes
[ ] No
N/A
-
Samples: Samples are optionally provided that preconfigure items of their type their type to help customers get started more easily.
[x] Samples not provided
[ ] Samples for pre-configuration of items provided
-
Custom Actions: Custom actions can be optionally provided as a part of the item editor.
[x] Custom Actions are not implemented
[ ] Custom Actions implemented as part of Workload
N/A
-
Workspace settings: Workspace settings provide a way that workloads can be configured on a workspace level.
[ ] Supported
[x] Not Supported
-
Global Search: Searching for items in Fabric is supported through the top search bar.
[ ] Supported
[x] Not supported
Security / Compliance Requirements:
-
Security general: Protection of customer data and metadata is of paramount importance. Workloads must go through a security review and assessment. Vendor attests that the security review and assessment was completed and will be periodically performed as enhancements and changes are made. Security issues discovered which could have a detrimental impact on the customer should be addressed promptly and customers notified where applicable.
We are fully SOC2 compliant. We don’t host this information publicly but users can request a copy by sending an email to support@osmos.io
-
Privacy: Partners that build workloads also have a responsibility to protect that data when they access it. Every workload goes through a privacy assessment and a privacy review. Vendor attests that privacy review was completed and is periodically performed as enhancements and changes are made.
[x] Extra Requirements:Vendor attests that only essential HTTP-only cookies are used by the Workload and only after positively authenticating the user.
N/A
-
Data Residency: MicrosoftFabric is making an Enterprise Promise around data not leaving the geography of the tenant for stored data and data in transit. As a workload in Fabric directly and users need to be aware what your commitments to Data Residency are. Define what your commitments are to the Data Residency of customer data.
Our approach to data residency is documented here: https://docs.osmos.io/security
-
Compliance: The publisher attests to the following security, data and compliance regulations and standards
Osmos is a cloud hosted solution and utilizes Microsoft Azure and another cloud services provider as its web security and web application firewall providers, serving as a critical line of defense against potential malicious activity.
Our infrastructure is developed primarily in the Rust Programming Language. This provides memory safety (like Java) while providing the performance of C/C++. Given that our infrastructure packs and unpacks customer data, this provides a foundational level of security against security issues like buffer overflows. High-risk data transformations are done inside Web Assembly sandboxes to provide additional security.
All data, both in transit and at rest, is encrypted utilizing the 256 key bit Advanced Encryption Standard (AES).
https://docs.osmos.io/security
Support:
-
Live site: Partner workloads are an integral part of Fabric that require the Microsoft support teams need to be aware of how to contact you in case customers are reaching out to us directly.
Microsoft direct vendor outreach:
[x] Contact Name/Team:
Sandy Daniels/Customer Success
[ ] Number
[x] Email alias
support@osmos.io
[x] Self Service portal
None. Users email support@osmos.io for help.
-
Supportability: Vendors are responsible for defining and documenting their support parameters (Service level agreement, contact methods, ...). This information needs to be linked from the Workload page and should always be accessible to customers. In addition, the Marketplace criteria, need to be taken into account for the listing of the SaaS offer.
[x] Vendor attests that support information is published to the marketplace offering and available to user/customers directly via the workload
-
Service Health and Availability: Vendors need to host a service health dashboard that shows their service health and availability to customers. This information can be included on the Supportability page.
Every tenant has a completely separate control plane so there is nothing global to ping that would provide insight to paying customers.
Fabric Features:
-
Application Life Cycle Management (ALM):Microsoft Fabric's lifecycle management tools enable efficient product development, continuous updates, fast releases, and ongoing feature enhancements.
[ ] Supported
[x] Not Supported
-
Private Links: In Fabric, you can configure and use an endpoint that allows your organization to access Fabric privately.
[ ] Supported
[x] Not Supported
-
Data Hub: The OneLake data hub makes it easy to find, explore, and use the Fabric data items in your organization that you have access to. It provides information about the items and entry points for working with them. If you're implementing a Data Item, show up in the Data Hub as well.
[ ] Supported
[x] Not Supported
-
Data Lineage: In modern business intelligence (BI) projects, understanding the flow of data from the data source to its destination can be a challenge. The challenge is even bigger if you built advanced analytical projects spanning multiple data sources, data items, and dependencies. Questions like "What happens if I change this data?" or "Why isn't this report up to date?" can be hard to answer.
[ ] Supported
[x] Not Supported
-
Sensitivity labels: Sensitivity labels from Microsoft Purview Information Protection on items can guard your sensitive content against unauthorized data access and leakage. They're a key component in helping your organization meet its governance and compliance requirements. Labeling your data correctly with sensitivity labels ensures that only authorized people can access your data.
Extra requirements:
For partners that are using Export functionality within their Item they need to follow the guidelines.
[ ] Supported
[x] Not Supported
Additional Notes
Please use this section to provide any further explanations, references, or notes that may be relevant to your attestation: