eSignature now available worldwide
We’re excited to share that eSignature for Microsoft 365 is now available worldwide* on Microsoft 365 public clouds allowing signatures to be requested on all PDFs and Word documents stored in SharePoint. This pertains to all PDFs and Word documents stored in SharePoint. Previously, this service was limited to the US, UK, EU, Canada and Australia-Pacific regions. Worldwide availability also includes the integration of Adobe Acrobat Sign and Docusign eSignature for PDFs on SharePoint. Signatures made simple We’re also excited to announce several updates to eSignature that make requesting and managing signed documents easier: eSignature for Word (Desktop) is now available to Word users on the Microsoft 365 Current Channel. eSignature for Word and PDFs is now available worldwide (while previously it was limited to certain regions). We’re adding a new free-text field capability for Word electronic signature requests. We’ve enhanced the signed PDF automatic save back capability with Adobe & Docusign signature services. Lastly, if you’ve been using “SharePoint eSignature”, you’ll notice it will soon have a new name in the UI, “Microsoft 365 eSignature”, reflecting that it’s a core part of the Microsoft 365 experience. Request electronic signatures from Word - Launched Microsoft Word now has built-in eSignature support for everyone on the Microsoft 365 Current Channel. This means you can initiate the signing process without ever leaving Word. No more toggling between multiple applications as you can add signature fields and send out for signatures directly from Word. Watch the eSignature for Word video to learn more about it. How it works: In Word (Desktop), open a document that’s stored in a SharePoint site with eSignature enabled. Once enabled by your administrator, you’ll find an “eSignature fields” option on the Insert tab of the ribbon. Click it to insert signature fields where needed in your document. Once you’ve placed the fields, you can enter the recipients’ email addresses (and optionally include a custom message), then hit “Create request”. Word will automatically convert the document to PDF for signing and send it out, all in one go. The signed PDF is saved right back into the SharePoint library next to your original Word file. In other words, your document never leaves your Microsoft 365 tenant during the process. And because your document and the signed copies remain in Microsoft 365, you retain full control over security and compliance. There’s no need to send files through external channels or as email attachments. New free-text field for Word documents – rolling out in October We’ve also added a new field to make your signature requests more powerful: free-text fields. This allows you to include additional input fields to your documents for signers to fill out when they sign, beyond just their signature or initials. A free-text field is a blank text field you can place in a document (just like a signature line or date field). When your signer is completing the signature request, they will see this field and can type in the information you requested. You can use it to gather any extra details you need. For example, you might ask the signer to provide their job title, an ID number, a mailing address, or any other relevant information while signing the document. This feature is great for scenarios where a signature alone isn’t enough and you had to chase down extra info via email or separate forms. Now you can capture that information in one step, during the signing process itself. Automatic save to original location – now available If you already use Adobe Acrobat Sign or Docusign eSignature for electronic signatures, you can leverage the eSignature for Microsoft 365 experience to initiate the request and have a copy of the signed PDF automatically saved back to the originating SharePoint library. This will help save your time in creating and finding signed PDFs. Users can create PDF signature requests from a SharePoint document library and choose one of those providers (if enabled by an admin) as the signing service. The PDF will be automatically uploaded to the provider to create a signing request. When signed, a copy of the signed PDF is automatically saved back into the original SharePoint library (whereas previously the signed PDF was saved back to a single dedicated provider folder). Next steps These updates (a new name, global availability, Word integration, custom fields, and third-party updates) all aim to make eSignature more convenient for you. If you’re an admin or interested user, make sure eSignature is enabled in your tenant. It’s found under Pay-as-you-go services in the Microsoft 365 Admin Center. Check that your Office apps are updated so you can see the Word integration. And give these new features a try! To learn more about eSignature configuration and usage, check out Overview of eSignature page on Microsoft Learn For a view of previous updates please see here: Announcing SharePoint eSignature for Microsoft Word | Microsoft Community Hub SharePoint eSignature product updates! | Microsoft Community Hub *Worldwide availability excludes Indonesia and Türkiye
Syntex creates only Single line text fields for each piece of information.
I have deployed and applied "Structured document processing" model to one of my libraries in SharePoint. I chose two pieces of information to extract: Date (type date) Table, which had 6 columns (with types : text, number, date) The training of the model and the extraction itself seems fine, but after applying the model to the library, all the columns, that Syntex creates in the library for the new content type are "Single lines of text". No number, no date... Is there something I am missing or is this the Syntex situation right now? Similar problem is with longer strings, where I would like the Syntex to grap the whole string, but since he is not able to create Multi line column, he just cuts the string after the character limit is reached. Any advice for how to proceed would be highly appreciated. Thanks!
Issues with Microsoft Syntex Document Processing Model: Incomplete Extraction for Multi-Page PDFs
I'm facing several challenges with the Microsoft Syntex document processing model, particularly when dealing with multi-page PDFs and large tables. I'd appreciate any insights or suggestions from fellow users or Microsoft experts who may have encountered similar issues. Below are the specific problems I'm experiencing: Unsupported PDF Formats & Multiple Tables on a Single Page: Some PDFs that I try to process seem to be in unsupported formats. In addition, pages containing multiple tables often result in extraction errors or incomplete data. Has anyone else encountered this with complex table layouts in PDFs, and what approaches have you used to resolve it? Data Extraction from Multi-Page PDFs: When processing PDFs longer than two pages (e.g., six-page PDFs), the model often extracts data correctly from only the first two or three pages. The remaining pages, particularly those with tables spanning multiple pages, are either incomplete or entirely missing. Additionally, large tables (100+ rows) in multi-page PDFs tend to result in inaccurate extraction. Are there any best practices for handling these multi-page table scenarios? Automatic Processing Issues: Sometimes, the Syntex model doesn't process files automatically. I have to manually select the file and click "Classify" to trigger processing. Is this a known issue, or is there something I might be missing in my setup? Model Publishing Delays: After publishing changes to the model, it often takes an extended period (up to 30 minutes or more) for the new model to start processing files. In some cases, the files aren't processed at all. Has anyone experienced similar delays after publishing a model, and what could be causing this? Low Confidence Scores for Multi-Page PDFs: When processing multi-page PDFs with tables, the model returns low confidence scores (below 60%). What steps can I take to improve these accuracy scores, particularly for documents with complex table structures?
Unable to train Syntex Structured Document model
Hi all, I am trying to create and train a Syntex model for the first time in my organization. I am going through the Content Center and, while a model is created when I hit the New Model button, when it goes to start the training process, I get the following error: I have confirmed that there exists an entry for SharePointFormProcessing in a table called Packages in Dataverse. The same thing happens when trying to create a model locally in another site and regardless of whether I'm using a the freeform selection or layout method. Does anyone have an idea what the problem might be?High costs for MS Syntex - although restricted to some sites - maybe open for a short time
Hi everyone, we are experiencing high costs for MS Syntex. We just wanted it to use for some sites - so i restricted it to 2 sites. But i did not see that i need to restrict each service - so some users seem to "use" it. How can i identify these sites and stop them from using any of the services? How can i completely disabled Syntex for our tenant if nothing else works? BR StephanBecome a Microsoft advanced content management advocate! [Opportunity]
The Microsoft Next Gen Content Services team is launching an advanced content management and experiences Advocates Initiative. We are looking for thought leaders who can amplify product awareness for the latest innovations from SharePoint Premium, SharePoint Embedded, Microsoft 365 Backup, and Microsoft 365 Archive. As advocates, you can help create content to share with your networks, leveraging Microsoft marketing material and updates. If you or anyone you know would be interested in posting about these solutions, please fill out our interest form. As a member of this initiative, you’ll have opportunities to cross-promote on Microsoft channels, receive marketing updates on the products, and enhance your personal brand.
Files getting classified in syntex training files but not in SharePoint library
Hi, I'm having some trouble with some files in SharePoint not getting classified, with some appearing to not even get put through the classification process. The files are being scanned in batches, uploaded, run through Adobe's OCR, and then classified. However, random files will just never get classified, because of one of two reasons: they never get classified (aka they have no classification date whatsoever), or they get "classified" but remain as the default content type ('Document'). In either case, if I then copy the file into the training files for the model that should be classifying it (there are multiple models running on the same library in our case), the model will perfectly classify it as positive. I can then save/sync the model and reupload the file, and it will still present the same problem. Does anyone know what may be causing this? To be clear, I have had this happen across multiple files, which are being uploaded in batches, with 80-90% of the files in a batch being classified just fine but some just refusing to do so. I can have file 1, 2, and 3 work fine in a batch but suddenly file 4 will fail. There is no difference between the files in terms of scanning, OCR, or the upload process, so I have tentatively ruled out those being the issue. I'm assuming it's a Syntex issue, at least for the second category because those files are getting run through it, just not being classified properly. Any help would be much appreciated!Microsoft Syntex Licencing
Since the per-user licence is no longer available (as of July 1st, 2023), can I use all features with a pay-as-you-go licence? Features like uloading content to a library where a custom model has been applied only have been availbe for users with a per-user licence. How can I use those features if the corresponding licence isn't available anymore? Grateful for any input on this one!
