Microsoft SharePoint helps teams share and manage documents, lists and information. Service Automation Suite connects that content to requests, records and outcomes in other applications. Documents remain in the agreed location while teams find the right information alongside their work.
The work between your applications
Work from Microsoft SharePoint. Connect the next step.
Microsoft SharePoint helps teams share and manage documents, lists and information. Service Automation Suite connects that content to requests, records and outcomes in other applications. Documents remain in the agreed location while teams find the right information alongside their work.
A change, request or alert
Service Automation Suite
Data, people, assets and relationships on one foundation.
Compare
What exists? What should exist?
Determine what is needed
Matrix · policy · legal requirements
Coordinate the next steps
Checks · tasks · approvals · actions
Execution ↔ feedback
Your people and tools
Microsoft SharePointMicrosoft Dynamics 365
For example. Also with other teams, suppliers and applications.
Verify. Inform. Report.
What is complete? Who needs to act? Which exception needs attention?
Start with one integration, register or check. Build on the same data and rules.
Lists & records
A SharePoint list need not remain isolated.
Use a managed list as an agreed source or align relevant data with other records. Define ownership of its content.
Service Automation Suite · Central coordination
Relate data, verify and determine follow-up
Add a central register and source-of-truth rules. Check differences, request missing data and determine what gets updated.
Work from Microsoft SharePoint
Microsoft SharePoint
Lists & records
For example, with
Your other teams and applications
Agree the source
Define authoritative columns, their owner and the records that should follow.
Match the same record
Use stable identifiers and check existing data before updating.
Track changes and differences
Update agreed fields and have missing values or conflicts reviewed.
Documents & records
The right SharePoint document with the right request.
Connect documents in the agreed library to requests and records in other applications. Content remains managed in SharePoint.
Service Automation Suite · Central coordination
Relate data, verify and determine follow-up
Combine the data with your policy, risk assessments and checks. Request information or a decision where needed, track actions and record the outcome.
Work from Microsoft SharePoint
Microsoft SharePoint
Documents & records
For example, with
Microsoft Dynamics 365
Your other teams and applications
Define where the document belongs
Choose the library, record and attributes used to identify the request.
Connect the reference and context
Connect the agreed document reference and metadata to the request without unnecessary copies.
Respect access controls
Retain agreed SharePoint permissions. A document link does not grant permission to open its content.
Workflow outcome
Work completed. Records updated too.
Return a confirmed workflow outcome to the agreed document or list record. Teams need not re-enter completion separately.
Service Automation Suite · Central coordination
Relate data, verify and determine follow-up
Combine the data with your policy, risk assessments and checks. Request information or a decision where needed, track actions and record the outcome.
Work from Microsoft SharePoint
Microsoft SharePoint
Workflow outcome
For example, with
Your other teams and applications
Use a confirmed outcome
Define the completed step allowed to trigger a SharePoint update.
Update only agreed fields
Match the outcome to the correct record and update relevant metadata or list fields.
Verify the record
Record what changed. Follow up missing documents or insufficient permissions deliberately.
Under the hood
How to connect, test and manage the integration.
For administrators who want to understand how it works: connect Microsoft SharePoint to your other applications, map the data and use the response in the next step. Configure it centrally in Service Automation Suite.
Agree access and application scope
This example concerns SharePoint Online through Microsoft Graph. Select required sites, lists and document libraries with appropriate permissions. A document link does not automatically grant access. Review SharePoint Server separately.
Choose the API method, URL and authentication. Manage the host and credentials in an environment. Test a request in Discovery and inspect the fields actually returned by the API.
Build the request body from validated data and inspect Body Preview before testing. Use the result ID in Data Context for the next request or save output to an entity. Configure write-back separately.
Configure error rules by HTTP code and/or message. A temporary API failure can use bounded retries. A missing relationship or rejection needs another route: record the cause and configure a verification task for the appropriate team, for example.
Which data do you maintain?
An example configuration, not fixed field names or a mandatory combination.
Record ID, document and recipient
Validate the agreed data and record its relationship to the external request.
Request reference and status
Use the available API status for follow-up, distinguishing completion, rejection, expiry and technical failures.
Document and confirmed outcome
Store the available result with the related record. A sent request is not yet a completed activity.
Sent ≠ processed. Use the response and agreed validation to determine the next step.
Need to publish data yourself?
Use Endpoint Composer to publish a configured Service Automation Suite data object. Choose read and write methods and security profiles so a customer can retrieve agreed service data or a supplier can submit information, for example. Configure data selection and subsequent processing separately.
Combine the integration with a form, a shared matrix, a review or collaboration between service teams. For example, an approved request leads to execution in Microsoft Entra, a ValidSign signature request and feedback in TOPdesk. Your process determines the steps needed; not every use case requires all these components.
Start with one use case. Connect customer, employee and asset data, for example, and agree which source is authoritative. Reuse those relationships, a matrix where needed and configured actions in the next workflow. Agree who maintains the data and rules. Expand without repeatedly connecting and maintaining the same information.
Signature declined. Keep the process moving.
A request awaits a ValidSign signature. Declining, expiry and technical failure each need different handling.
Combine
Link the request, signing request and document. Read the available status and apply agreed conditions to determine the next action.
The outcome determines what follows
Signed: process the document and confirm the activity. Declined: route the reason to the owner. Temporary technical failure: retry only under the configured error rule.
The benefit
Appropriate follow-up for each outcome without counting a sent signing request as completed work.
Temporary access, with the end handled too.
Additional access is approved for a limited period. A checkbox alone does not preserve why, for whom and until when.
Combine
Connect identity, approval, expiry date and the available access action. Reuse the same data for a scheduled follow-up check.
The outcome determines what follows
Revocation confirmed: record the result. Extension requested: ask for a new decision. Not revoked: raise the exception with the authorised group rather than silently completing it.
The benefit
Fewer forgotten exceptions and a traceable relationship between approval and actual access.
A different name does not mean a new record.
A person or organisation has a different name in the source than at a customer or supplier. Matching text again can create incorrect or duplicate relationships.
Combine
Retain verified identifiers and source rules in a shared table. Reuse the relationship for requests, tickets and other integrations.
The outcome determines what follows
Known key: use the relationship. Multiple candidates or a missing identifier: request review. Once confirmed, reuse the established relationship.
The benefit
A consistent data foundation managed by your team instead of investigated again for every connection.
Your process needs more than a standard action?
Configure the missing API request, input and output in API Composer. Use its response in the next step and combine it with data tables, forms and automations. Extend the same product and reuse the configured building blocks.
Use Service Automation Suite to update a ticket in TOPdesk, for example, with fields available through its API, such as category, priority, status and support group. For another application, configure its request and field mapping. The outcome determines the next action: confirm, add information or request review, not merely check whether the request arrived.
Need to publish data or let others submit it? Endpoint Composer exposes a configured Service Automation Suite data object with selected methods and security profiles. Other building blocks handle subsequent processing.
From product to workflow
Microsoft SharePoint in your wider workflow
Pull up a chair. Or join us online.
Over coffee, tea or online: tell us what you are working on.
We can help with the integrations, automation and coordination your process needs, even if your application is not listed yet.
Microsoft Dynamics 365
Microsoft SharePoint
