Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content
Switch branches/tags
Go to file
Cannot retrieve contributors at this time
title description ms.author author manager ms.date audience ms.topic ms.service ms.collection ms.custom search.appverid ms.localizationpriority
Get started driving adoption of Microsoft SharePoint Syntex
Learn how to use and implement SharePoint Syntex in your organization to help you streamline your business processes.

Get started driving adoption of Microsoft SharePoint Syntex

Think of the intelligent content services available in SharePoint Syntex as having three parts:

  • Content understanding: Create no-code AI models to classify and extract information from content to automatically apply metadata for knowledge discovery and reuse. Learn more about content understanding.
  • Content processing: Automate capture, ingestion, and categorization of content and streamline content-centric processes using Power Automate. Learn more about content processing.
  • Content compliance: Control and manage content to improve security and governance with integration to Microsoft Purview Information Protection.

With new AI services and capabilities, you can build content understanding and classification apps directly into the content management flow using SharePoint Syntex. There are two different ways of understanding your content. The model type you use is based on file format and use case.

Form processing Document understanding
Created from document library. Created in the content center, part of SharePoint Syntex.
Model created in AI builder. Model created in native interface.
Used for semi-structured file formats. Used for unstructured file formats.
Settable classifier. Trainable classifier with optional extractors.
Restricted to a single library. Can be applied to multiple libraries.
Train on PDF, JPG, PNG format, total 50 MB/500 pp. Train on 5-10 PDF, Office, or email files, including negative examples.

For a more complete comparison of the capabilities, see Difference between document understanding and form processing models.

Identify pilot business scenarios to optimize

To prepare for using SharePoint Syntex in your organization, you first need to understand the scenarios in which it will be useful. The "why" helps determine what model will be needed, and how to structure your org based on where the model will be applied. Here are a few scenarios where document understanding can help your organization:

  • Content processing: Process contracts, statements of work, and other form-like documents. Intake the forms, train the model to understand and map the fields, and then run your forms through to automatically collect the data. For more information, see Form processing overview.
  • Invoice analysis: Pull out the relevant details from your invoices and make sure they're complying with policy or are being processed appropriately.

Think about ways that SharePoint Syntex can help your organization:

  • Automate business processes
  • Improve search accuracy
  • Manage compliance risk

When thinking about which business scenarios to consider, ask yourself the following questions:

  • Does it solve a real problem?
  • Will it be widely used or have broad impact?
  • Is it obtainable?
  • Can you measure success?

Prioritize scenarios based on impact and ease of implementation. Make your initial focus area higher impact scenarios that can also be easily implemented. De-prioritize lower impact scenarios that are hard to implement.

Use the example scenarios and use cases to prompt ideas about how you can use SharePoint Syntex in your organization.

Identify roles & responsibilities

Determine who in your organization will build and manage the models. The following roles might be involved.

SharePoint/Knowledge admin Power Platform admin Knowledge manager Model owner
AAD role AAD role AAD role Champions
Configure form processing Configure Dataverse environment for form processing Gather use cases Gather business use cases
Manage content centers and permissions Purchase and allocate AIB credits Establish best practices and review model analytics Create and apply models

Knowledge manager, Business Process Owner, and Content model owner create sample models and champion adoption in the organization. Others who may be involved: Compliance admin, Taxonomy managers.

Where will they build and apply the models? Are there existing processes or repositories that could be enhanced?

  • Form processing: Decide which sites will get Form processing action.
  • Document understanding: You can create multiple content centers for different business areas.

Strategic positioning

Work with stakeholders to make sure they are aligned on the strategy for using SharePoint Syntex. Research and provide the following resources to help with this positioning:

  • Business outcomes:
    • Potential fiscal outcomes
    • Potential agility outcomes
    • Business outcome template
  • Stakeholders/Exec sponsor buy-in/alignment
    • Business case decks
    • Financial models
    • Company readiness - culture

Identify stakeholders

Identify the stakeholders for your project.

Role Responsibilities Department
Executive sponsor(s) Communicate high-level vision and values to the company Executive leadership
Project lead(s) Oversee the entire launch execution and rollout process Project management
Knowledge administrators Create and manage the content centers IT or other department
Content managers and model owners Gather use cases and create and apply models Any department
Champions Help evangelize and manage objection handling Any department (staff)
Tenant administrator Configure tenant-level settings IT department
Power Platform administrator Configure Dataverse environment IT department

[!NOTE] Though we recommend having each of these roles fulfilled throughout your rollout, you may find that you don't require them all to get started with your identified solution.

Readiness checklist

To get ready for implementing SharePoint Syntex, you need to:

Readiness for Content Understanding.

  1. Plan the end state
    • Document understanding models are the means, not the end.
    • Plan for harnessing the value of extracted metadata with:
      • Search
      • Filtering and view formatting
      • Compliance
      • Automation
  2. Identify
    • Understand existing information architecture and content management feature use.
    • Are any existing content types good candidates for models?
    • What existing processes would be improved by metadata?
  3. Design
    • Design your approach to information architecture, managed metadata and content types.
    • Design the process for definition, creation, management.

Engage your organization

  1. Identify stake holders, confirm scenarios, and develop project plan.
  2. Configure settings and apply licenses.
  3. Begin awareness and training – Recruit Champions.
  4. Roll out in stages.
  5. Gather feedback and iterate.
  6. As usage grows plan for any AI Builder credits as needed.

See also

Scenarios and use cases for SharePoint Syntex

Manage contracts using a Microsoft 365 solution