Select Your Region

Visit the Cary, NC, US corporate headquarters site

Americas

Europe

Middle East & Africa

Asia Pacific

View our worldwide contacts list for help finding your region

Americas

Europe

Middle East & Africa

Asia Pacific

Sign In

Get access to My SAS, trials, communities and more.

Sign Out

Get access to My SAS, trials, communities and more.

SAS Sites

sas.com
Support
Blogs
Communities
Developer
Curiosity
Videos

Documentation

Learn
Brand
PartnerNet
Merchandise
  1. SAS Support
  2. SAS Decision Builder Attestation

SAS Decision Builder Attestation

Revised: September 26, 2025

Publish Workload Requirements Attestation Checklist


We, the vendor, SAS Institute Inc., 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:

  1. Value To Customers: The workload provides the following value to customers –

    SAS Decision Builder is a powerful, SaaS solution designed to help organizations automate, optimize, and scale their decision-making processes. Whether you're managing complex business rules, integrating machine learning models, or using Python code, SAS Decision Builder allows you to create intelligent decision flows that drive actionable insights in real-time.

    With seamless integration into the Microsoft Fabric ecosystem, SAS Decision Builder helps businesses streamline workflows, improve operational efficiency, and make smarter, data-driven decisions. Effortlessly connect to Azure services, deploy machine learning models, and monitor decision performance - all from a single platform.

  2. 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 Trials1

    [] Yes                      [X] No

    SAS Decision Builder will enter public preview with the delivery of email to customer within 5 seconds which will have enablement materials.

  3. Monetization: The workload is available on the marketplace for the customer to procure with or without a trial in accordance with the monetization guidelines2

    [X] Yes                    [] No

    SAS Decision Builder on Fabric Workload: https://app.fabric.microsoft.com/workloadhub/detail/SAS.DecisionBuilder.Product?experience=SAS.DecisionBuilder.Product

 

Technical Requirements:

  1. Microsoft Entra Access: The workload(s) use Microsoft Entra authentication and authorization3.

    [x] No additional authentication and authorization mechanisms are used
    [ ] Additional authentication and authorization mechanisms are used for stored data In Fabric

  2. One Lake: Workloads integrate with One Lake4 to store data in the standard formats supported by the Fabric platform so that other services can take advantage of it.

    [ ] All data and metadata is stored in One Lake or Fabric Data Stores
    [x] Not all data and metadata is store in One Lake or Fabric Data Stores

    Metadata related to the definition of decisioning resources are stored in a database contained on the cluster which houses the Decision Builder workload. All input/output data used in executing decision flows IS stored in One Lake.

  3. 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 access5.

    [ ]  The service works in its entirety with even if customers enable this functionality
    [x]  The service works in with limitations if customers enable this functionality
    [ ]  The service does not work Microsoft Entra Conditional Access

  4. 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

  5. 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

  6. 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 tenants6 can potentially be granted access to items partners are creating.

    [ ] Cross tenant B2B collaboration supported
    [x] Workload Item Access only within the tenant

    Testing of this path has not been possible and thus we are unable to state that it is supported

  7. 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.

    SAS does have a well thought out, detailed Business Continuity Plan.

  8. Performance: The Workload implementation takes measures to test and track performance of their Items

    [ ] Performance Metrics on workload performance  are available via the monitoring hub
    [ ] Workload additionally includes a separate monitoring UI to test and track performance
    [X] 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

  9. Presence: To ensure that customer expectations independent of their home or capacity region are met, vendors need to align with fabric regions7 and clouds. Availability in certain restrictions also impacts your Data Residency commitments.

    [x] Service availability and colocation/alignment in the following fabric regions
    US, Canada, Europe and UK
    [ ] All or part of the service does not reside in Azure

  10. Public APIs: Fabric Public APIs8 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:

  1. Common UX: The workload and all item types the partner provides as part of it comply with the Fabric UX guidelines9.

    [x] The following variance and/or exceptions have been granted by Microsoft
    SAS has attempted to meet UX guidelines provided by Microsoft.  We await a list of items from Microsoft detailing where our interpretation of the guidelines is wrong.

  2. Item Creation Experience: The item creation experience is in accordance with the Fabric UX System10.

    [x] Yes
    [ ] No

  3. Monitoring Hub: All Long running operations need to integrate with Fabric Monitoring Hub11.
    [x] Yes
    [ ] No

  4. Trial Experience:The workload provides a Trial Experience for users as outlined in the design guidelines12
    [ ] Trial Supported
    [X] Trial Not Supported

  5. Monetization Experience: The monetization experience is in line with the design guidelines13 provided

    [x] The monetization experience is completely integrated with the market place and compliant with the guidelines
    [] Bring Your Own License (BYOL)
    [] Free / Freemium
    [ ] Other

  6. Accessibility: The user experience is in compliance with the Fabric UX design guidelines for Accessibility14

    [ ] The user experience is completely compliant with the guidelines
    [x] The following limitations exist

    SAS’ Accessibility Standard governs the conformance of SAS products, documentation, training, and support materials with level AA of the Web Content Accessibility Guidelines version 2.2 (WCAG 2.2) as defined by the World Wide Web Consortium and included by reference in the Revised Section 508 Information and Communication Technology Standards and EN 301 549. The extent to which the proposed solution conforms with WCAG 2.2 AA varies by product. Accessibility conformance reports for SAS products are available on the SAS Accessibility Support Center at https://support.sas.com/accessibility/conformance/. Those conformance reports use the Voluntary Product Accessibility Template® (VPAT) as defined by the Information Technology Industry Council. SAS’ sole responsibility with respect to accessibility under this agreement is to publish accessibility conformance reports for SAS products. Please send questions about accessibility to accessibility@sas.com.


  7. 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

    Full I18n planned for GA

  8. Item Settings: Item settings are implemented as a part of the ribbon as outlined in the UX guidelines15

    [x] Yes
    [] No

  9. Samples: Samples are optionally provided that preconfigure items of their type their type to help customers get started more easily.

    [ ]  Samples not provided
    [x]  Samples for pre-configuration of items provided

  10. 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

  11. Workspace settings Workspace settings provide a way that workloads can be configured on a workspace level.

    [] Supported
    [x] Not Supported

  12. Global Search: Searching for items in Fabric is supported through the top search bar.

    [] Supported
    [x] Not supported

Security / Compliance Requirements

  1. Security general: Protection of customer data and metadata is of paramount importance16. 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.

    Please outline all the security and compliance tests, attestations performed. The more detailed this is the easier it is for customers/Microsoft to review. This should include references to the latest security assessment reports

    <List of custom actions>

  2. Privacy: Partners that build workloads also have a responsibility to protect17 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.

    [  ] Extra Requirements: Vendor attests that only essential HTTP-only cookies18 are used by the Workload and only after positively authenticating the user.

    • PEN testing

  3. Data Residency:  Microsoft Fabric is making an Enterprise Promise around data not leaving the geography19 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.

  4. Compliance: The publisher attests to the following security, data and compliance20 regulations and standards

• SAS Product Security Framework
• SAS Privacy Framework
• SAS Quality Imperative
• SAS Trust Center

Support

  1. 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:

    [ ] Contact Name/Team:

    SAS Customer Engagement

    [ ] Number        

    919-677-8000

    [ ] Email alias  

    contact@sas.com

    [ ] Self Service portal    

    https://communities.sas.com


  2. Supportability21: 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 Marketplace22 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


  3. 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.

    Service heath dashboard can be found here:

    <URL to service health dashboard>

Fabric Features:

  1. Application Life Cycle Management (ALM): Microsoft Fabric's lifecycle23 management tools enable efficient product development, continuous updates, fast releases, and ongoing feature enhancements.

    [] Supported
    [x] Not Supported

  2. Private Links: In Fabric, you can configure and use an endpoint24 that allows your organization to access Fabric privately.

    [] Supported
    [x] Not Supported

  3. Data Hub: The OneLake data hub25 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

  4. 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

  5. Sensitivity labels: Sensitivity labels26 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:

<Additional Notes by Vendor>

References

<Please consolidate all relevant reference here for completeness e.g. support policy, compliance, tos, service health etc. might seem redundant but useful to have it in a single place>

1 https://learn.microsoft.com/en-us/fabric/workload-development-kit/monetization#trials
2 https://learn.microsoft.com/en-us/fabric/workload-development-kit/monetization
3 https://learn.microsoft.com/en-us/fabric/workload-development-kit/authentication-concept
4 https://learn.microsoft.com/en-us/fabric/onelake/onelake-overview
5 https://learn.microsoft.com/en-us/fabric/security/security-conditional-access
6 https://learn.microsoft.com/en-us/fabric/security/security-b2b
7 https://learn.microsoft.com/en-us/fabric/admin/region-availability
8 https://learn.microsoft.com/en-us/rest/api/fabric/articles/
9 https://aka.ms/fabricux
10 https://aka.ms/fabricux
11 https://learn.microsoft.com/en-us/fabric/workload-development-kit/monitoring-hub
12 https://aka.ms/fabrictemplates
13 https://aka.ms/fabrictemplates
14 https://aka.ms/fabricux
15 https://aka.ms/fabricux
16 https://learn.microsoft.com/en-us/fabric/governance/governance-compliance-overview#secure-protect-and-comply
17 https://learn.microsoft.com/en-us/fabric/governance/governance-compliance-overview#secure-protect-and-comply
18 https://learn.microsoft.com/en-us/dynamics365/commerce/cookie-compliance
19 https://azure.microsoft.com/explore/global-infrastructure/data-residency/
20 https://learn.microsoft.com/en-us/fabric/governance/governance-compliance-overview
21 https://learn.microsoft.com/en-us/fabric/workload-development-kit/supportability
22 https://learn.microsoft.com/en-us/partner-center/marketplace-offers/marketplace-criteria-content-validation
23 https://learn.microsoft.com/en-us/fabric/cicd/cicd-overview
24 https://learn.microsoft.com/en-us/fabric/security/security-private-links-use
25 https://learn.microsoft.com/en-us/fabric/get-started/onelake-data-hub
26 https://learn.microsoft.com/en-us/fabric/get-started/apply-sensitivity-labels