Tuesday, 17 January 2023

Syntex Pay As You Go - how it helps and how to use it

In previous articles I've covered many of the capabilities of Syntex and how it can be used, and from my perspective organisations are becoming very interested in Syntex to automate processes involving documents. In a notable development Syntex now has a Pay As You Go (PAYG) model for pricing - in preview until February/March 2023 with no costs charged. In the same approach used for Power Platform PAYG, Azure billing is used and charges appear in Azure Cost Management within the subscription linked to your Microsoft 365 tenant. In this article we'll consider cases where the PAYG may be more appropriate than the 'per seat' licensing model, how to configure it, and considerations for using it. A big factor here is precisely which Syntex features are available in the PAYG model - it's not all of them, and Microsoft are starting in some places and expanding over time.

Why use PAYG for Syntex?
In short, many processes you might automate with Syntex don't align well with a small, specific group of employees who will consistently use the capability (suited to the per seat licensing model). Some do of course - the finance team who are using Syntex to automate invoice processing or receipt analysis, or the research analysts who need automated tagging and powerful search across articles they create. However, sometimes we want all employees to participate in a process where Syntex is used despite the fact this only happens occasionally. Examples could include:
  • Processes and documents related to an event - a webinar, or month-end/year-end processes, company results time etc.
  • An organisational CV store where any employee can upload and maintain their CV
  • Using Syntex for governance i.e. the AI detecting sensitive data in documents in order to automatically apply a sensitivity label in Microsoft 365 - to drive encryption, conditional access, or other security measures
  • Using Syntex for compliance - driving automated retention labels to ensure content isn't retained for longer than permitted
These examples all relate to Syntex content understanding capabilities i.e. Syntex analysing and/or extracting contents of your documents to do something with that. 

On the content creation side, Syntex Content Assembly might be used to generate new documents in an automated (or semi-automated) way by many people but only occasionally. Perhaps it's a large team of engineers who occasionally create risk assessments or safety reports, or a finance or HR process which creates a document but can be triggered by a large number of people.

Other areas where it will often make sense to pay as you go relates to Syntex content management capabilities coming later in 2023, such as eSignatures. PAYG will be very relevant here - see my list lower down.

Which Syntex capabilities can be used with PAYG?

Let's break it down into what's here today (January 2023) and what's coming tomorrow.


  • NEW - Unstructured document processing
  • Structured document processing (via AI Builder)
  • Freeform document processing (via AI Builder)
In short, all document understanding capabilities can now be used via PAYG (subject to preview conditions until Febrary/March 2023 - more on that later). The fact this now includes arguably the most powerful type, unstructured document processing, is significant.


Note: This is my list, not Microsoft's. While Microsoft have not announced that Syntex PAYG will support all the big features coming this year, given the nature of the 'content transactions' in these areas I think it's a reasonable bet that Syntex PAYG will support all of these in time:    

  • Content Assembly
  • Image tagging
  • Translations 
  • Summarisations
  • Backup/restore
  • Archiving
  • Syntex eSignatures (forthcoming alternative to DocuSign and Adobe Sign) 

How much does Syntex cost under PAYG?

Each type of operation (e.g. a document being understood by Syntex, or a document being created by Syntex Content Assembly) will have it's own cost - and Microsoft have not yet announced pricing as of January 2023. Logically, I'd expect pricing models to look something like this:

Capability Charged by
Content assembly Per document generated
Syntex eSignatures Per signature
Syntex backup/restore Volume of data (and perhaps number of restores)
Syntex archiving Volume of data (and perhaps access frequency or volume of data accessed)
Syntex document summarisation/translation/image tagging etc. Per item processed

Regardless of the specifics, this will give 'pay per use' consumption pricing which should make Syntex appealing to many organisations. Simpler than 3rd party products which compete with some of these features, no wastage, and for orgs bought into Syntex no complex planning for exactly who should get a Syntex license and how to force processes around that.

A note on the PAYG preview (running until Febrary/March 2023):

For the preview period, unstructured document processing (the key new item in the 'today' category above) is 100% free - and no predicted costs show on the bill, because pricing hasn't been announced. What you do get to see is how many documents are being processed and in which sites in your tenant. The idea is for organisations already using Syntex with licensed users to have a method of measuring consumption and therefore having a means of calculating costs based on real usage when PAYG becomes available. However, I'm not sure how valuable this personally since relatively few businesses are in production with fully-enabled Syntex processes today - seeing consumption across a bunch of POC test cases isn't too helpful.

Configuring Syntex PAYG

You need the following:

  • An Azure subscription in the same tenant
  • A resource group in Azure to use for the Syntex billing resources
  • An Azure storage account - used to store Excel exports showing Syntex billing

Step 1 - associate Syntex billing in M365 to Azure

To set up we start in the Microsoft 365 admin portal. Head to the 'Setup' area followed by the Syntex configuration option within the 'Files and content' section:

Here you'll see a new item to set up billing: 

In here you need to select the Azure subscription, resource group and region to use for billing storage:

Once that's done the initial configuration starts to happen:

Step 2 - configure Syntex billing exports to Azure storage

So far we've just told Syntex that we do want to use PAYG - this makes it available in the tenant (i.e. to non-licensed users), but what's needed now is the ability to monitor costs. Since this is done in Azure, head into your subscription. The first thing we need is a storage container to hold the files, so let's create that first - you can have the Azure wizard create the storage container for you, but generally better to do quick one-off steps manually so you truly know where things are. I named my container "syntex" (needs to be lower case):

We now configure the export. This ensures the Excel billing files showing your Syntex consumption will be exported regularly from Microsoft 365 to Azure so you can monitor and analyse. To do this, go to the Cost Management blade and then into the 'Exports' area:

Now we select the options for the export. You'll generally want to see actual costs (the alternative is an ammortised view) and I chose the  'daily' option to get a new file each day - in production you may be happy with weekly or monthly:

The storage container is also chosen at this point (select the 'use existing' option if you created it already):

Once this is done the export is set up:


Syntex billing reports

Once the export has been processed files will start to appear in your selected Azure container, with a folder for each export configured:

Drilling into the containers will take you to the Excel files. Once downloaded, you'll see data for all your Azure operations so if it's a busy subscription there'll be a lot in there. To isolate the Syntex rows, add an Excel filter on a column such as:
  • meterCategory = Syntex

This will give you a view of your Syntex PAYG transactions:

  • Today you'll only see 'Document Understanding' items, but in the future you'll see transactions for Syntex eSignatures, Content Assembly, backup/restore actions etc. A number of fields reflect this, including 'ProductName'
  • The 'tags' field - this gives details of the  SharePoint sites and libraries where the Syntex AI model processed the document, helping you understand the actions your users are taking and in which
  • The 'quantity' field - this relates to the number of pages processed by Syntex AI, across all processed documents 
  • At the moment, some useful details such as the specific Syntex AI model used and precisely who is triggering consumption does NOT come through to the logs. This is a shame because being able to see 'invoice processing' and 'contracts model' etc. would simplify understanding how Syntex is being used a lot. Let's hope additional detail like this comes through in the future  
  • Preview note - since Syntex PAYG is free in the preview period the 'effectivePrice' is 0 - so as described above, the preview doesn't help you fully predict costs at the moment, but does convey usage - which you can use when pricing is announced

How do I predict and stay in control of Syntex PAYG costs?
As usual with Azure billing, the answer is by configuring budgets and alerts

Using the metadata for Syntex operations which comes through to Azure billing, we can create a budget within Azure Cost Management to alert an operations team that consumption is higher than expected - at which point some investigation and/or intervention action can occur. In common with Azure Cost Management in general, we can't set an absolute limit at which point consumption is blocked - and indeed, most organisations wouldn't this for production processes. The last thing you want at month end is to discover invoices are no longer being processed and for it to take a day to find out why. But Azure budgets and alerts give you the foundations to implement the control processes you need.

Let's look at this in the next section.

Configuring an Azure budget to stay in control of Syntex PAYG costs

To configure budgets and alerts for Syntex consumption, head into the Azure Cost Management and then into 'Budgets'. 

The key step is to add a filter for one of the Syntex fields - for example 'MeterCategory = Syntex':

As more Syntex capabilities arrive which support PAYG, you could choose to be more specific e.g. monitor spending on document understanding specifically:

The next step is to configure the alert so that someone is notified at the right point (e.g. 80% of the forecast OR actual spend has been reached):
Once you have the budgets configured as you need, admins can track and forecast Syntex PAYG costs as we progress through a month or quarter, and you're in control of your spend. Job done.


Being able to pay only for what you use opens the door to Syntex adoption without an extensive business case and/or complex licensing decisions. As of January 2023 the capability is only in preview, and only for Syntex unstructured document understanding - the other two document processing flavours (unstructured and freeform) are already covered since they are charged through AI Builder credits in the Power Platform. However, this is the first truly native Syntex capability to get PAYG - and in the future we can expect Content Assembly, eSignatures, backup/restore, archiving and other Syntex capabilities to be charged in this way or at least have a PAYG option. Having this done through Azure Cost Management provides an existing model which admins in most organisations will already be very familiar with. 

Sunday, 27 November 2022

Microsoft Syntex - December 2022 update and compiled articles

Microsoft Syntex has been one of Microsoft's biggest announcements in 2022 - which can be somewhat confusing because it existed previously as SharePoint Syntex since 2020 - but Syntex is expanding massively from "AI that understands your documents so you can automate processes" to an entire suite of advanced capabilities related not just to your documents, but also your images and videos. Some of the bigger recent or forthcoming features include document eSignatures, annotations, image recognition, automated document summaries and translations, auto video transcription and much more - many of which were announced at Microsoft's Ignite conference in October 2022. I'm hearing Microsoft folks say that "Syntex could be as big or bigger than the Power Platform in time", which is an interesting thought given the impact that has had.

Over the last 2 years I've been writing a lot about Syntex on this blog and thought it would be good time to do two things:
  • Provide a 'Syntex on a page' round-up of the current and future capabilities    
  • Provide links to my Syntex articles from one place
This article provides both of those.

Syntex on a page - December 2022

If you're confused about what's in Syntex and what's coming, I like to put things into these buckets:
  • Content understanding and processing - using AI to understand your documents and automate something 
    • Example - find all risk assessments missing a start date and contact the supplier organisation
    • Example - read an insurance contract and save the policy details to a database
  • Content assembly - automated creation of new documents
    • Example - generate a new contract for every new starter
  • Content management and governance - premium document management capabilities 
    • Example - send a completed contract for eSignature (like DocuSign or Adobe Sign but fully integrated into Microsoft 365) and move location once complete
    • Example - automated detection of pay review documents so specific security or policies can be applied without manual tagging 
The image below (click to enlarge) shows what's in Syntex today and what's in the roadmap:

Hopefully that helps position the today/tomorrow capabilities somewhat.

Compilation of my articles

I’ve been slowly creating a back catalogue of Syntex articles as I research, learn, and write about the technology. I’ve covered concepts such as training Syntex to read and understand documents, extracting data from forms, automating the creation of new documents, using Syntex in a fully automated process (Straight Through Processing) and various hints and tips articles. Here's a list of Syntex articles which might be useful, starting with the fundamentals and moving into more advanced topics:
Note that there have been some renames along the way, and some of those articles might contain the old names. Here are some examples:
  • SharePoint Syntex -> Microsoft Syntex
  • Document understanding -> Unstructured document processing
  • Forms Processing -> Structured document processing
Hopefully the links above are useful on your Syntex learning journey.

Reminder - why is Syntex important?

One way or another, automation will always be a theme of many of the I.T. projects undertaken in the next few years. The trend is increasing, with analysts predicting a $30b market by 2024 (IDC) and Gartner saying 60% of organisations are pursuing four or more automation initiatives. There are many technologies in the space, but Microsoft Syntex changes the game because advanced AI and document automation tools are now baked into the core productivity platform used by 91% the world’s top businesses (i.e. Microsoft 365) - inexpensive, readily available and democratised for every business.
It's no surprise Microsoft are investing heavily here. Every organisation has thousands of processes needing human input. If you consider Financial Services as just one industry, banks deal with applications for loans, mortgages, credit cards, loyalty schemes and many other products. Insurance companies quote, sell, and renew policies for home, car, travel, pet cover and more – and those are just the obvious products and services. Zooming out, every industry you can think of has an entire ecosystem of processes that can be optimised.
As Syntex powers are amplified and more capabilities are added, spending time evaluating what Syntex can unlock is likely to be valuable for many organisations. 

Wednesday, 7 September 2022

SharePoint Syntex - new support for full document automation scenarios with Power Automate

SharePoint Syntex, the AI-enabled document automation capability within Microsoft 365, has steadily been increasing in features since its introduction in October 2020. In relative terms Syntex is still quite a young product, and seeing the new features emerge it's clear that Microsoft are investing heavily in this area. If you're not familiar, Syntex offers a range of capabilities including:

  • Automated creation of documents from your templates (known as Content Assembly)
  • Automated classification and understanding of documents - once Syntex AI is trained it can not only identify and recognise your different document types (contracts, invoices, CVs, safety reports, sign-off sheets etc.) but also extract key elements. Pulling the recommendations from a safety report could be one example of this. Often, you'll build a more significant automated process around this, for instance notifying a specialist team or inserting into a database or ERP system
  • Automated content compliance - since Syntex AI can automatically classify your document types from the contents, it can be used to protect and manage content. One example might be adding a sensitivity or retention label to a document identified as a CV - thus ensuring Conditional Access policies are applied or that a disposition process is triggered after a certain number of years

Until now, one of the missing pieces was the ability to fully automate Syntex. When using Content Assembly to create documents for example, it was necessary for a human to click a button to actually trigger the document creation, and this was required on a one-by-one basis (for more details on bulk document creation Syntex see my guide Automate creation of new documents with SharePoint Syntex Content Assembly). This was a real constraint on Syntex for genuine end-to-end automation, otherwise known as Straight Through Processing (STP), because clearly if a human needs to trigger the process then by definition you don't have full automation. 

As expected, Microsoft have now solved this by integrating Syntex with Power Automate.

Two main scenarios for Syntex integration
While there are a million use cases for using Syntex (and Intelligent Document Processing in general), fundamentally there are two patterns which underpin pretty much all of them:
  • Automating the creation of a document - i.e. automated use of Syntex Content Assembly
  • Automating a downstream process once Syntex has 'read and understood' a document - i.e. steps triggered when Syntex has completed its Content Understanding process
Microsoft now address both of these fundamental needs with the Power Automate integration - there is one new trigger and one new action.

Let's look at both scenarios individually.

Fully automated document generation with Syntex Content Assembly

Previously, it was possible to automate most but not all steps to create a document with Syntex Content Assembly. You could set up your Syntex document template with placeholders for values to be dropped in, and you could create data rows representing individual document instances to be created from the template - these are usually SharePoint list items for Syntex. What you couldn't do is create 100 documents instantly using this combination of template and data - but now you can. 

Microsoft have introduced a new Power Automate action for Syntex. At the time of writing (August 2022) it's currently in preview and is labelled "Generate document using SharePoint Syntex"):

When using this action, you need to point it to your document template by providing the site, document library and template file name:

Once these details are provided the Power Automate action dynamically discovers your Syntex placeholders in the template and allows you to specify a value for each:

This allows you to drop values into your predefined placeholders within the document being generated. The most common way of doing this in Syntex Content Assembly is through SharePoint list items - you simply add an item to this list for each document you wish to create. In my demo scenario from previous Content Assembly articles, I'm using job role descriptions:

Now we have the full Syntex automation in Power Automate, we can do better than clicking a button to create each document from the ingredients. You can build whatever automation you need, but a common pattern will be to create the document as a new item is added to your SharePoint list - so in my example, every time a new C+C role is added to the list, the corresponding role description document is generated with values dropped into the placeholders. To do this, simply map the fields in the Power Automate action to the columns in your SharePoint list:

The document is now generated automatically and saved into SharePoint, with the specific role details (department, location, working hours etc.) dropped into the placeholders:

So that's document assembly. But what if you want to automate a process based on a document being classified and understood by Syntex?

Automating a process based on Syntex document understanding

For people new to Syntex and document automation, sometimes it can be difficult to envisage which processes document understanding can make a substantial difference to. It comes down to how a document is used once it has been created. We use documents for different purposes of course - sometimes simply to capture knowledge, but on other occasions for humans to use in a process such as a review or to use to start a new process. Here the document is typically created in one place and the information within it used in another, and every business has many instances of this. With Syntex, the ability to recognise document types and extract key information for it to be used in some way is what makes it game-changing - the use cases are endless. Here are some examples from my organisation (Content+Cloud) and some of our clients:

At C+C:
  • Using Syntex to read our draft Statement of Work documents - automatically notify our teams of total value of SOWs created this week and any instances of missing details (e.g. project manager)
  • Using Syntex to read Excel project pricing workbooks (used to generate project estimates quickly in pre-sales before any formal project setup) - thus helping us derive project themes and trends from all opportunities we're estimating, not just projects we're delivering
At some of our clients:
  • Using Syntex to extract risks and safety methods from risk assessments - to identify gaps and missing information so that appropriate teams can be notified, and the risk addressed
  • Using Syntex to clauses from a contract - to highlight areas of concern for investigation
  • Using Syntex to extract recommendations from safety reports 
  • Using Syntex to extract core information from 'lead lawyer' notes
Needless to say, common document types like contracts, invoices, CVs, loan agreements, credit applications etc. are all fertile ground for intelligent document automation.

Automating processes based on document contents

To automate document understanding in this way, we look to the Syntex Power Automate trigger which has been introduced:
To illustrate usage, here's an example using (redacted) Statement of Work documents from our projects - before the 'full' automation, Syntex is already recognising our SOWs and extracting the engagement value, Business Manager, Exec Sponsor, Project Manager and so on:

In this scenario, to build a further 'downstream' automation based on this we use the Power Automate trigger - it recognises the extracted pieces of data for me to automate based on them:
Once the trigger has executed, all the pieces of information Syntex has extracted from the document are available to the Flow:
This will be specific to your scenario and Syntex AI model of course. If your Syntex extractors are pulling the candidate name, address, notice period and salary expectations from a CV or cover sheet then that's what will be available to make decisions on and process in your Flow.

In my Statement of Work example, let's say we wanted to post in a Teams channel if a Statement of Work was discovered without a Project Manager being referenced:

The result being:

To summarise, Syntex is recognising the document as a C+C Statement of Work, extracting details of the engagement, and automatically flagging any SOWs without a project manager specified. The ingredients used here and this type of 'quality checking' of documents is extremely powerful and can be applied to so many cases. It's a great example of intelligent automation at work.   


As I'm fond of saying, Syntex is game-changing because advanced AI and document automation tools are now coming to the masses by being baked into Microsoft 365 and SharePoint. 

Syntex was originally released to the world needing a human to trigger the document creation or document reading/understanding process, which got in the way of fully automating significant processes (or resorting to work arounds). Microsoft have now completed the circle on this, and it's another milestone in Syntex maturity and value. Microsoft's future roadmap for Syntex looks healthy, and whether you call it Intelligent Automation, Intelligent Document Processing, Hyperautomation, or something else, we should expect a lot more from the Syntex and the capability area Microsoft describe as Content Services in the future.

Wednesday, 27 July 2022

Identifying Syntex use cases - how the SharePoint Syntex assessment tool can help

If you're a regular reader of this blog, you'll know I'm a big advocate of what Microsoft are doing with SharePoint Syntex. In short, Syntex brings intelligent automation to every organisation for processes which involve documents - and in most businesses today, that's a substantial proportion of processes. We're in the middle of big shift in technology where cloud power is commoditising advanced AI and automation capabilities so that they are no longer restricted to expensive, specialist, and often industry-specific tools. Examples of this include the legal and engineering sectors, in which it has been common to invest in specialist proposal generation and contract automation software, but usually at significant cost. Instead, these AI and automation tools are now baked into core platforms such as Microsoft 365 and democratised so that 'ordinary' employees can tap into them - add-on licensing might be required, but these tools have never so widely available. 

As market awareness grows, Syntex is forming quite a few of my client conversations at the moment. Organisations are considering how this new tool could help them, and in common with other innovative technologies one of the challenges is identifying use cases within the business where Syntex could have a big impact. I have a lot of thoughts on this in general, but one thing Microsoft have done to help is release the Microsoft 365 Assessment Tool (gradually replacing what was the PnP Modernization Scanner) which now has a 'Syntex mode' specifically - this can be used to assess your tenant and usage for Syntex automation opportunities. The idea is that by scanning your SharePoint landscape and IA for certain characteristics, this could uncover areas of the business using SharePoint in certain ways where Syntex could help. In reality, Syntex really shines where documents are part of a complex or time-consuming process - and a tool can only go so far in identifying that. But the idea has merit, so let's explore what the tool provides and how it's used.

Later, we'll also consider a more rounded approach to identifying document automation and Syntex opportunities.

What the Syntex Assessment Tool provides

Once you've done the work to install and configure the tool (covered below), an assessment is run to scan your Microsoft 365 tenant in 'Syntex adoption' mode. This launches a scanning process across your entire SharePoint Online estate which, depending on tenant size, will take some time. Once execution is complete, a Power BI report is created as the output - allowing you to slice and drill around your data in later analysis. The theme of the tool is to identify areas of 'SharePoint intensity' - examples include your largest document libraries or document libraries where custom columns and/or content types have been created. Other insights include your most heavily used content types and libraries with names matching common Syntex usages (e.g. invoices and contracts). The full list of report elements and descriptions from the tool is:

  • Libraries with custom columns - Identify libraries where Syntex can automatically populate columns, improving consistency
  • Column usage - Identify patterns of column usage, to target Syntex models where they will have the maximum benefit 
  • Libraries with custom content types - Identify libraries using custom content types, where Syntex models can be used to automatically categorize files. 
  • Content type usage - Identify patterns of content type usage, to target Syntex models where they will have the maximum benefit
  • Libraries with retention labels - Identify libraries where retention labels are used, where Syntex can be used to automate and improve consistency
  • Library size - Identify large libraries where classification and metadata can improve the content discovery experience
  • Library modernization status - Identify libraries which may need to be modernized to fully make use of Syntex
  • Prebuilt model candidates - Identify libraries where names or content types suggest a prebuilt model could be applied
  • Syntex model usage - Review the current use of Syntex models in your site
So that's an overview but it's more helpful to look at the results of running the tool - the sections below dive in into the output, and then towards the end we'll zoom out again to consider the role of the tool overall. 

Looking at real-life results - the Power BI report from my tenant

The screenshots below show the report output from one of my tenants - this isn't a production tenant but does have 1000+ sites and several years of activity.

Assessment overview

Provides an overview of the assessment run you performed, covering how many sites were processed successfully vs. any failures. I had 15 failures out of 1169 site collections for example:


Libraries with custom columns

A fairly useful indicator of 'SharePoint intensity', because if lots of columns have been created it shows that tagging/metadata is important here. This could indicate that having Syntex extractors automatically tag each document could be powerful. I have 574 such libraries in my tenant:


Column usage

Similar to the above, but focused on re-use of your custom columns and most common custom column types:


Libraries with custom content types

Again, a potential sign that files here are important because the library is using custom content types:


Content type usage

Gives you insight into your top content types - how many lists each one is applied to, how many items are assigned to the content type etc.


Libraries with retention labels

You might ask 'how are retention labels relevant to Syntex'? Remember that a key Syntex capability relates to information governance - the ability to automatically recognise potentially sensitive documents from their contents (e.g. contracts, CVs, NDAs, HR documents etc.) and ensure they are retained (or disposed of) with appropriate compliance. Since this is a non-production tenant I don't have too much of this, but you may do:


Library size

Again, knowing where your biggest libraries are can help you understand SharePoint hot spots, where many documents potentially relate to a process:


SharePoint modernisation status

This one is less directly connected to Syntex (relating as it does to the modern/classic status of the library in general), but relevant because Syntex can only be used on modern libraries. If you find important libraries still in classic status, you'll need to modernise them for the Syntex options to show up:

Prebuilt model candidates

Syntex ships with prebuilt AI models for receipts and invoices. This report element is simple but can be highly effective - essentially, 'find all the libraries in my tenant which have receipt or invoice in the name'. Most likely your production tenant *will* have this content somewhere, and Syntex could help provide insights or automate processes here:


Syntex model usage

This last page in the report gives insight into any existing Syntex usage in your tenant. In my case I have 8 models, and because none of them have recently executed the number of items classified in the last 30 days shows as 0:

So that's the tool output. Now let's turn our attention to how to run it in your tenant. 

Running the Microsoft 365 assessment tool

The tool itself is command-line based, hosted on GitHub, and comes in Windows, macOS and Linux flavours. Here's what you'll need:
  • A machine to run the tool
  • The tool downloaded from GitHub - see Releases · pnp/pnpassessment · GitHub
  • To register an AAD app with certificate-based auth - you'll register this in your tenant to allow the tool read access to your sites and workflows
The tool itself has a mode to help create the self-signed cert and get the AAD app registered. The command to do this is detailed on the Authentication page in the documentation. Most likely you will want to register a dedicated app for this tool rather than piggy-back on something else, because any SPO throttling will then be first restricted to this app rather than a critical production solution you have. 

The permissions required may need some thought because the 'optimal' permissions (which are needed for a full assessment) for application scope are:
  • Graph: Sites.Read.All
  • SharePoint: Sites.FullControl.All
The tool can perform a less complete audit with more restrictive permissions however - you'll get a less informative report with some sections missing, and whether that provides enough decision-making info to you is for you to decide. All of this is documented on the Permission Requirements page in the docs.

Once you're set up with authentication, it's a matter of running the tool in Syntex mode with the --syntexfull flag (if that's the assessment type you're able to run):

microsoft365-assessment.exe start --mode syntex --authmode application ` --tenant chrisobrienXX.sharepoint.com --applicationid [AAD app ID] ` --certpath "[cert path and thumbprint]" ` --syntexfull
Your Power BI report will emerge once the tool has trawled through your SharePoint estate.


So we've seen how the tool is used and what the report provides. But what value does it provide in the real world?

My recommendation - use the tool as ONE input
It was a great idea to extend the Microsoft 365 assessment tool for Syntex, and I fully agree that there are certain indicators of SharePoint use that align strongly with Syntex. However, the tool is no substitute for real process mining in your organisation - and I've no doubt the tool creators (the Microsoft PnP team) take the same view. My recommendation is to use the tool if you can, but perhaps think of it as background research before talking to the business. When working with a client to identify possible scenarios to automate with Syntex it's useful to talk to different teams and functions. I like to ask questions like these to uncover situations where Syntex automation could add high value:
  • Which document types are most important to the business? Why?
  • What types of documents do you have which are time or labour intensive (for people to read and process or create)?
  • What types of documents do you have which have a significant process around them?
  • What types of documents do you create in large volumes?
  • Which documents are part of a transmittal or submittal process? In other words, which documents are exchanged with other parties rather than spend their entire lifecycle within your organisation?
  • Which documents contain sensitive information, and should therefore potentially have information protection policies applied to them to support compliance?

Hopefully this analysis of the Syntex assessment tool has been useful. Syntex is a powerful tool to bring automation to an organisation's critical processes and we're going to see a lot more of it in the future.

Thursday, 30 June 2022

Speaking at ESPC 2022 (Copenhagen) on SharePoint Syntex and Viva Topics

Process automation and AI will be big growth engines for technology in the next few years, so I'm really happy to have been selected as the speaker to cover these hot topics (and how the Microsoft stack solves for them) at one of the big Microsoft conferences this year. The European SharePoint, Microsoft 365 and Azure Conference will be in Copenhagen, Denmark from 28th November - 1st December 2022, meaning I've got plenty of time to practice my speaker face and bad jokes. I'll be delivering two sessions:

SharePoint Syntex - art of the possible and lessons learnt (session code T29)

Tuesday 29th November, 15:15

Session abstract:

Organisations using Microsoft 365 are waking up to the potential of SharePoint Syntex to have a dramatic impact on their business. Syntex provides AI capabilities to 'read documents for you', allowing your Microsoft tenant to recognise your individual document types, extract meaning, and automate processes - with these ingredients the possibilities are endless. We've implemented Syntex to read safety reports, risk assessments, project plans and more, learning a lot about how things work in practice and the pitfalls that will cost you time or lead to poor results.

In this session we'll discuss potential use cases, what you can expect from Syntex, key decision points, and down to important tips such as how to work with documents containing tables. Over the course of several demos we'll walk through the end-to-end of creating and tuning Syntex AI models, building automations, and even advanced scenarios such as adding Power BI dashboards to drive process compliance.

We'll complete the session with a discussion on licensing and roadmap, so you leave armed with everything you need to get achieve more with SharePoint Syntex.

Viva Topics 18 months later - what did we get?  (session code W16)

Wednesday 30th November, 11:45

Session abstract:

Finding information and expertise is far too time-consuming in the vast majority of organisations. Poorly configured search, the sprawl of repositories and sites, unceasing content growth and difficulties recognising authoritative content all conspire against the information worker. No wonder McKinsey and IDC report that the average knowledge worker spends 20-30% of their time just looking for things.

Viva Topics is Microsoft's answer to this challenge. After being part of the Project Cortex private preview, we've had 18 months of Viva Topics being live in our business and have implemented the technology for several clients. This session covers the benefits we've seen (both the expected and unexpected), and shares best practice guidance on how to plan, implement, and build on Viva Topics. We'll demo the technology in our production environment so you can see the experience in action.

Implementing Viva Topics at scale can be a big investment and it's important to know what's coming in the future. We'll end with a discussion on Microsoft's future roadmap and capabilities, so you can plan ahead with confidence.

Conference details

The tagline for the event is "Europe’s premier Microsoft 365 & Azure Conference" and that's probably a fair statement - I always really enjoy speaking at this event and being immersed in the great conversations which happen there. As usual, there's extremely strong representation from Microsoft too - keynote speakers include: 
  • Jeff Teper - CVP, Microsoft 365 Collaboration with Teams, SharePoint, OneDrive, Microsoft
  • Scott Hanselman - CVP, Microsoft 365 Collaboration with Teams, SharePoint, OneDrive, Microsoft
  • Karuana Gatimu – Principal Manager, Customer Advocacy Group, Microsoft Teams Engineering Microsoft
  • Vesa Juvonen - Principal Program Manager Microsoft
The overall conference programme and list of speakers make for a compelling event in my eyes. Over 2500 attendees are expected, and the conference should be a great mix of sessions and networking with many experts, partners and vendors in the Microsoft cloud space. 

Here's the link to the conference pricing page

Hopefully see you there!

Wednesday, 8 June 2022

SharePoint Content Assembly - hints and tips

In recent articles I've covered SharePoint Syntex from a few angles. Most recently in Automate creation of new documents with SharePoint Syntex Content Assembly we looked at exactly that, automated document creation using the scenario of role description documents, showing the end-to-end process of using Content Assembly. Here at Content+Cloud the scenario is a good fit for Syntex in our business because we have a large number of open roles, which equals a large number of documents, and they're all based on our common template for role descriptions. With Syntex Content Assembly we can simply create an item in a SharePoint list, run the process, and have a Word document created in our C+C branded format which combines the individual specifics for a new role with our standard content on benefits, pension, approach to hybrid work, office locations, and so on.

Having spent some time with Syntex Content Assembly, in this post I want to share some tips which might accelerate your understanding.

Syntex Content Assembly tips

Tip #1 - Understand the 1:1 relationship between your Syntex modern template and where it's created

Syntex Content Assembly is based on creation of a 'modern template', a new construct in Microsoft 365 and SharePoint which acts as the base template for the Word documents you are going to create. One aspect of Content Assembly which needs consideration is that today the template lives in the SharePoint document library you create it in - and nowhere else. There is a 1:1 mapping between your template and this document library: 

What this means is that if you'd like to generate documents from this template across your tenant (e.g. different business units) you'll need to recreate the modern template in multiple locations. An alternative approach could be to centralise the creation process into one doc lib and then use Power Automate to 'send' the created document instances to where they need to be. Either way, you need to consider this as a primary consideration when working with Syntex.

Tip #2 - Syntex Content Assembly stores modern templates in the hidden 'Forms' area in the document library 

Building on the first tip, it's useful for more technical SharePoint people to understand where modern templates are stored in SharePoint's internals. The answer is they get stored in the hidden 'Forms' directory inside the document library you create the template in. You'll never see this in the SharePoint front-end, but using a tool like the SharePoint Client Browser allows you to see this - specifically a subfolder created within 'Forms' which has the name of your template with spaces removed. In here you'll see the .docx or .pptx file for your template:  

Armed with this knowledge, if you have access to SharePoint development skills it's certainly possible to create a single Syntex modern template and use it in multiple locations across your tenant. Use of SharePoint file/folder APIs is the key (perhaps with PnP or a SharePoint migration tool to help), but you could nominate one location as a master and ensure the template is synchronised to other locations. To put this in context, one example could be if your organisation has multiple countries and each should use the same role description template - by synchronising updates to the modern template with each of the locations, you can effectively use one shared template globally. 

Tip #3 - keep up with Syntex capability updates: things are changing! 

Content Assembly, like the rest of Syntex, is moving fast and it's worth monitoring the Microsoft 365 to see what's coming. As a great example, when I started writing this article (May 2022) one annoying limitation was that you couldn't have Content Assembly drop values into a table within a Word template. This was frustrating because it's common for a document template to have a table (or several) containing different values in each created document - our C+C role description document has core role details such as title, hours, department, reporting line etc. in a table for instance. When using Syntex Content Assembly a few weeks ago, we needed to reformat the document template to remove the tables because Syntex would give messages like this:

But no more!

Another great capability launched in the last few weeks is the ability to create PDF documents (not just Word) using Syntex Content Assembly - this came in late May/early June. So, stay on top of things by going to the Microsoft 365 roadmap and filtering on Syntex

Tip #4 - deal with pre-requisites first: create the SharePoint list/taxonomy and have the document ready

Having been through the process a few times, one recommendation I have with Content Assembly is to ensure you have your prerequisites created and to hand before you go through the 'modern template' creation process. Not doing this is the equivalent of trying to book a holiday without your credit card or passport number to hand - you'll only get so far before realising you need to stop, gather up some things, and most likely abandon the process to restart later. 

With Syntex Content Assembly, you map placeholders in your document to the columns in the SharePoint list (or taxonomy terms) where the data will be pulled from - so it makes sense that in the mapping process the source data needs to exist for it to be selected. In the example below these are shown in the right-hand panel by Syntex:

There are actually a couple of variants here - consider that in Syntex Content Assembly, the value to be dropped into a particular placeholder in your document can come from:
  • A particular column value in a SharePoint list item (likely to be the most common case)
  • A term in a SharePoint taxonomy term set
  • A one-off value entered manually by the user 
So what we're really saying is that in the first two cases, make sure the SharePoint 'thing' exists first. When using list items for your document creation process, creating the underlying SharePoint list first is important - even if you only create the list and define the columns but don't yet add any data. To put this in context, my SharePoint list for C+C roles looks like the image below - the columns on the right are multi-line fields with lots of detail on the specific role so I've blurred those out, but hopefully the consideration is clear:

In summary, make sure the list and columns (or taxonomy term set) exist before creating the Syntex modern template so that you can map to them.

Tip #5 - avoid SharePoint rich HTML fields with Syntex Content Assembly

There a few 'compatibility' considerations but one in particular I'd like to call out is that SharePoint fields containing HTML (e.g. for rich formatting such as bullet lists, tables, font styles etc.) won't come over to your document well. Your formatting will be lost and you'll see raw HTML in your Word document like this:

To avoid this, ensure any multi-line SharePoint fields are plain text only:
Other restrictions include:
  • Only Word/PDF are supported for now - no PowerPoint or Excel
  • Your Word template cannot have comments or Track Changes enabled
  • Content controls in Word (remember those?) are not supported
  • Images cannot be dropped into the document - only text
In addition to the Microsoft 365 roadmap for high level details, see the 'Current release limitations' section of the Microsoft documentation on Syntex Content Assembly to keep up with these constraints and new capabilities as Syntex evolves.


Despite being a relatively new technology Syntex doesn't have too many foibles. Microsoft are putting advanced process automation capabilities into the hands of every (licensed) Microsoft 365 and SharePoint user here, the Content Assembly feature ticks the box of generating new documents as the counterpart to core the Syntex ability of reading, understanding, classifying, and extracting key information from documents. On the document generation side, in addition to the lower-level constraints listed above, it's worth remembering of course that the document creation process still involves a couple of clicks - we still don't have end-to-end automation without human involvement. However, we can be sure that will appear on the roadmap soon most likely through Power Automate integration. Syntex has a bright future as an automation enabler which is relevant to almost every sector and organisation - understanding how to approach Syntex and some of the implications of the model is important to get the most value. Hopefully this post has been useful.