Technical scope & prerequisites
The Automation Office 365 Action Pack integrates Microsoft 365 SharePoint file operations into Automic Automation workflows. It ships a set of public actions for uploading, downloading and deleting files on SharePoint plus connection-management actions to register Azure app credentials. All SharePoint calls authenticate against Microsoft Graph using the client-credentials flow and run through Automic’s WebService REST agent.
This Full Guide covers the scope, installation, configuration, complete action reference, and upgrade path. It is the authoritative technical document for Automic administrators and platform owners deploying the Automation Office 365 Action Pack into a production Automic environment.
Supported platforms
- Automic Automation: V24 and later release lines
- SharePoint: SharePoint Online (Microsoft 365) via Microsoft Graph API
- Authentication: Microsoft Entra ID (formerly Azure AD) app registration with client-credentials flow
Prerequisites on the Automic side
- A running Automic Automation system with an accessible tenant (client) other than client 0 — the Action Pack cannot be installed into client 0
- A configured WebService REST agent reachable by the tenant in which the Action Pack is installed
- An OS agent and a matching login object — required only for the upload action when Delete source = true and for the download action when local sub-directories must be created
- Optional: the dependent Action Pack PCK.ITPA_SHARED — install it first if it is not already present in the target client
Prerequisites on the Microsoft 365 side
- An Entra ID (Azure AD) app registration with a generated client secret
- Tenant ID — the unique identifier of the Microsoft 365 / Entra ID tenant
- Client ID — the application (client) ID of the registered app
- Client secret — the secret value paired with the client ID
- API permission: Sites.ReadWrite.All (Application permission, not Delegated), granted admin consent
- Network reachability from the WebService REST agent to graph.microsoft.com and login.microsoftonline.com
Installation, update & uninstall
The Automation Office 365 Action Pack is installed through the standard Automic Administration → Packs interface. The same workflow covers fresh installation and in-place updates. All operations must be performed in a non-zero Automic client — installation into client 0 is not supported.
Installation / update
- Log in to the target Automic client (not client 0)
- Switch to the Administration view
- Open the Packs menu entry
- Optional: if not already installed, install the dependent Action Pack PCK.ITPA_SHARED first
- Click Install From File
- Select the Automation Office 365 Action Pack file and confirm with Install
- If a previous version is already installed, confirm the update by clicking Install again
- Confirm the successful installation with Close
After installation the Action Pack appears inside the PACKAGES folder of the Automic client.
Uninstall
- Log in to the Automic client where the Action Pack is installed
- Switch to the Administration view
- Open the Packs menu entry
- Select the Automation Office 365 Action Pack and click Remove
- Confirm the uninstall by clicking Yes
- Confirm successful removal with Close
Configuration — connecting to an Azure tenant
Before any SharePoint action can run, the Automation Office 365 Action Pack needs at least one named connection configuration pointing at an Entra ID / Azure tenant. Configurations are managed through three dedicated actions: CONFIGURATION_ADD, CONFIGURATION_UPDATE and CONFIGURATION_REMOVE. Every SharePoint action references a configuration by name at runtime.
Creating a new configuration
- Start the action CONFIGURATION_ADD
- Fill in the required fields (see parameter table below)
- Confirm by clicking Submit
Configuration parameters
| Parameter | Variable | Notes & example |
|---|---|---|
| Name | &AUT_O365_CONFIGURATION# |
Free-form configuration name. Recommended syntax: TENANT_APPID — e.g. MYCOMPANY_MYAPP or AUTOMIC_0100 |
| Tenant ID | &AUT_O365_TENANT_ID# |
The unique Tenant ID of the Azure / Entra ID environment to connect to |
| Client ID | &AUT_O365_CLIENT_ID# |
The unique Client ID of the registered app |
| Client Secret | &AUT_O365_CLIENT_SECRET# |
The client secret value paired with the Client ID |
| Grant Type | &AUT_O365_GRANT_TYPE# |
OAuth 2.0 grant type. Typical value: client_credentials |
| Scope | &AUT_O365_SCOPE# |
Microsoft Graph scope URL. Typical value: https://graph.microsoft.com/.default |
Updating and removing configurations
- To create additional configurations, start CONFIGURATION_ADD again with a new name
- To modify an existing configuration, run CONFIGURATION_UPDATE with the existing configuration name and the fields to change
- To delete a configuration, run CONFIGURATION_REMOVE with the configuration name as the only required parameter
Actions reference
The Automation Office 365 Action Pack exposes five public actions: two for connection management and three for SharePoint file operations. All SharePoint actions internally acquire an access token via Microsoft Graph, resolve the target site and library, and then execute the REST call through the WebService REST agent. The following sub-sections document every public action and its parameters.
4.1 · CONFIGURATION_ADD / CONFIGURATION_UPDATE
Create or update a named connection configuration used to authenticate against Microsoft Graph.
Object names:
- PCK.TRICISE_AUT_O365.PUB.ACTION.CONFIGURATION_ADD
- PCK.TRICISE_AUT_O365.PUB.ACTION.CONFIGURATION_UPDATE
Parameters: see the configuration parameter table in Section 3 above.
4.2 · CONFIGURATION_REMOVE
Remove an existing connection configuration.
Object name: PCK.TRICISE_AUT_O365.PUB.ACTION.CONFIGURATION_REMOVE
| Parameter | Variable | Notes & example |
|---|---|---|
| Name | &AUT_O365_CONFIGURATION# |
Existing configuration name — e.g. MYTENANT_APPID |
4.3 · SHAREPOINT_FILES_UPLOAD
Upload one or more local files to a SharePoint library via Microsoft Graph REST. File selection supports wildcards and optional recursive traversal of sub-directories; uploaded files can optionally be deleted from the source path after a successful transfer.
Object name: PCK.TRICISE_AUT_O365.PUB.ACTION.SHAREPOINT_FILES_UPLOAD
Internal sub-processes:
- SHAREPOINT_GET_TOKEN — acquires the Microsoft Graph access token
- SHAREPOINT_GET_SITE — resolves the target SharePoint site
- SHAREPOINT_FILES_UPLOAD → SHAREPOINT_FILE_UPLOAD — executes the upload per file
- SHAREPOINT_FILES_DELETE — invoked when
Delete source = trueto clean up the source after upload
| Parameter | Variable | Notes & example |
|---|---|---|
| Site Link | &AUT_O365_SITE_LINK# |
Unique SharePoint site reference. Example: mydomain.sharepoint.com:/sites/mySite |
| Library name | &AUT_O365_DRIVE_NAME# |
Target SharePoint library. The default library in SharePoint is “Freigegebene Dokumente” / “Shared Documents”. Example: Dokumente |
| Sharepoint path | &AUT_O365_SHAREPOINT_PATH# |
Target folder inside the library. Either the root (root) or a sub-folder (root:/MyFolder/MySubfolder). Example: root:/myFolder |
| Filepath pattern | &AUT_O365_FILE_PATTERN# |
File selection pattern. Fully qualified or wildcard. Example: *.txt |
| Local path | &AUT_O365_LOCAL_PATH# |
Local source directory containing the files to upload. Example: C:\temp |
| OS Agent | &AUT_O365_AGENT# |
Operating-system agent used for source deletion when Delete source = true. Example: MYAGENT |
| OS Login | &AUT_O365_LOGIN# |
Login object used for source deletion when Delete source = true. Example: LOGIN.MYLOGIN |
| Include Folders | &AUT_O365_RECURSIVE# |
Traverse sub-directories during upload. true / false |
| Delete source | &AUT_O365_DELETE_SOURCE# |
Delete uploaded files from the source path after a successful upload. true / false |
4.4 · SHAREPOINT_FILES_DOWNLOAD
Download one or more files from a SharePoint library to a local target directory via Microsoft Graph REST. Supports wildcard selection and optional recursive traversal of sub-folders.
Object name: PCK.TRICISE_AUT_O365.PUB.ACTION.SHAREPOINT_FILES_DOWNLOAD
Internal sub-processes:
- SHAREPOINT_GET_TOKEN — acquires the Microsoft Graph access token
- SHAREPOINT_GET_SITE — resolves the target SharePoint site
- SHAREPOINT_GET_ITEM_ID / SHAREPOINT_GET_ITEM_IDS — resolves single or multiple item IDs for the download
- SHAREPOINT_FILES_DOWNLOAD → SHAREPOINT_FILE_DOWNLOAD — executes the download per file
| Parameter | Variable | Notes & example |
|---|---|---|
| Site Link | &AUT_O365_SITE_LINK# |
Unique SharePoint site reference. Example: mydomain.sharepoint.com:/sites/mySite |
| Library name | &AUT_O365_DRIVE_NAME# |
Source SharePoint library. Default: “Shared Documents”. Example: Dokumente |
| Filepath pattern | &AUT_O365_FILE_PATTERN# |
File selection pattern. Fully qualified or wildcard. Example: *.txt |
| Sharepoint path | &AUT_O365_SHAREPOINT_PATH# |
Source folder inside the library. Root (root) or sub-folder (root:/MyFolder/MySubfolder) |
| Local path | &AUT_O365_LOCAL_PATH# |
Local target directory for downloaded files. Example: C:\temp |
| Include Folders | &AUT_O365_RECURSIVE# |
Traverse SharePoint sub-folders during download. true / false |
4.5 · SHAREPOINT_FILES_DELETE
Delete one or more files from a SharePoint library. Files are removed through Microsoft Graph REST, which moves them into the SharePoint recycle bin rather than permanently erasing them.
Object name: PCK.TRICISE_AUT_O365.PUB.ACTION.SHAREPOINT_FILES_DELETE
Internal sub-processes:
- SHAREPOINT_GET_TOKEN
- SHAREPOINT_GET_SITE
- SHAREPOINT_GET_ITEM_ID / SHAREPOINT_GET_ITEM_IDS
- SHAREPOINT_FILES_DELETE → SHAREPOINT_FILE_DELETE
| Parameter | Variable | Notes & example |
|---|---|---|
| Site Link | &AUT_O365_SITE_LINK# |
Unique SharePoint site reference. Example: mydomain.sharepoint.com:/sites/mySite |
| Library name | &AUT_O365_DRIVE_NAME# |
Source SharePoint library. Default: “Shared Documents” |
| Filepath pattern | &AUT_O365_FILE_PATTERN# |
File selection pattern. Fully qualified or wildcard. Example: *.txt |
| Sharepoint path | &AUT_O365_SHAREPOINT_PATH# |
Source folder inside the library. Root or sub-folder. Example: root:/myFolder |
| Include Folders | &AUT_O365_RECURSIVE# |
Traverse SharePoint sub-folders during deletion. true / false |
Upgrade & migration
Upgrading the Automation Office 365 Action Pack uses the same Install From File workflow as the initial installation. Automic recognises the existing installation and prompts for an update confirmation; selecting Install replaces the installed version in place. Configurations created through CONFIGURATION_ADD are preserved across upgrades.
Recommended upgrade procedure
- Back up or export the relevant tenant to retain a rollback point
- Pause any workflows that reference the Action Pack’s SharePoint actions
- Run Install From File with the new Action Pack file and confirm the update
- Smoke-test a known-good upload, download and delete action against a test SharePoint site
- Re-enable the paused workflows
Frequently asked questions
What does the Automation Office 365 Action Pack do?
The Automation Office 365 Action Pack adds SharePoint upload, download and delete to Automic Automation workflows. It wraps Microsoft Graph authentication, access-token handling and the REST calls into five public actions, so that file operations on SharePoint can be orchestrated directly from Automic without building a custom integration.
Which Automic versions are supported?
The Automation Office 365 Action Pack is supported on Automic Automation V24 and later release lines. Earlier V21 systems are not covered by the current release; Tricise provides compatibility updates as new Automic major versions arrive.
Which Microsoft Graph permissions does it need?
The Automation Office 365 Action Pack requires the Sites.ReadWrite.All Application permission (not Delegated) on the registered Entra ID app, with admin consent granted. The client-credentials OAuth 2.0 flow is used to obtain access tokens via login.microsoftonline.com and then calls Microsoft Graph at graph.microsoft.com.
Can the Action Pack target multiple Microsoft 365 tenants?
Yes. The Automation Office 365 Action Pack supports an unlimited number of named connections per Automic client. Each connection stores its own Tenant ID, Client ID, Client Secret, grant type and scope. Every SharePoint action references one configuration via the &AUT_O365_CONFIGURATION# parameter, which makes multi-tenant setups and cross-tenant file exchange straightforward.
Where is the Action Pack installed, and can I move it?
The Automation Office 365 Action Pack is installed into the PACKAGES folder of the Automic client via Administration → Packs → Install From File. The Action Pack must remain inside that folder and must not be renamed — doing either breaks internal references. Installation into client 0 is not supported.
Does the upload action require an OS agent?
The Automation Office 365 Action Pack upload action only needs an OS agent and login when Delete source = true, because source deletion runs on the filesystem where the uploaded files live. For pure uploads without source deletion, the WebService REST agent is sufficient. The download action uses the OS agent only when local sub-directories have to be created for a recursive download.
What happens when a delete action runs against SharePoint?
The Automation Office 365 Action Pack delete action does not hard-delete files. The matched items are moved into the SharePoint recycle bin via Microsoft Graph, which means they can be restored from the recycle bin within SharePoint’s retention window if a deletion turns out to be wrong.
Can filepath patterns use wildcards?
Yes. The &AUT_O365_FILE_PATTERN# parameter accepts both fully qualified file names and wildcard patterns such as *.txt or report_*.csv. Combined with the Include Folders flag, the Automation Office 365 Action Pack can process entire directory trees in a single action call.
How does upgrading to a new version work?
Upgrades of the Automation Office 365 Action Pack reuse the standard Install From File flow. Automic detects an existing installation, prompts for confirmation and replaces the Action Pack in place inside the PACKAGES folder. Named connection configurations created through CONFIGURATION_ADD are preserved across upgrades.
Does the Action Pack depend on other Tricise packs?
The Automation Office 365 Action Pack depends on PCK.ITPA_SHARED, a shared utility Action Pack. If it is not already present in the target Automic client, install it from the same Administration → Packs interface before installing the Office 365 Action Pack itself.
How much does the Automation Office 365 Action Pack cost?
The Automation Office 365 Action Pack is licensed as a one-time purchase at 3.200 € (excl. VAT) per Automic system. The price is shown on the Tricise shop page and includes Tricise product support plus compatibility updates for the current Automic V24+ release line. There is no recurring subscription fee.
Where can I buy the Automation Office 365 Action Pack?
The Automation Office 365 Action Pack is available through the Tricise shop at tricise.com/shop/automation-office-365. For questions around licensing, multi-system scoping, onboarding or live walkthroughs, contact Tricise through the consultation form.