Skip to main content
BOOK A DEMO

How to install skybow Background Automation services on SharePoint Server

skybow Support
  • Article Updated

skybow Background Automation Services is used for supporting Background features (Metadata Inheritance, Aggregation, Calculation Expressions, Scheduled Actions and Triggered Actions) in SharePoint server local environment. It is needed for:

This document describes how to deploy skybow Background Automation Services to your SharePoint server environment.

skybow Background Automation contains of:

  • IIS Site: skybow Background Automation
  • Windows services:
    • skybow Scheduled Action Job
    • skybow Queue Message Job
    • skybow Actions Job
    • skybow CleanUp Job
    • skybow HTTP Trigger Job
  • SharePoint SPFx Addin

Prerequsites: 

  • IIS (Internet Information Services)
  • SQL Server instance
  • MSMQ (Message Queuing)
  • PowerShell 5.0 or 5.1(Recommended)
  • User account for service identity:
     - This account will be prompted during the PowerShell deployment script (install_ba.ps1) and will be used as:
                   - Application Pool identity for the IIS site
                   - Log On account for all skybow Windows services
     -  Must have access to target SharePoint sites (be site collection administrator or be in the owners SharePoint group for the target sites)
     - Access to SQL Server is required only if DefaultConnection does not specify a custom SQL user in the connection string.
     - Must have permissions in Microsoft Message Queuing (MSMQ) for the private queues (Send, Receive and Peek permissions)    

Supported SharePoint Versions:

  • SharePoint Server 2019
  • SharePoint Subscription Edition (SE)

Installation Locations:

  • IIS site is installed at C:\inetpub\wwwroot\skybowBackgroundAutomation
  • Windows services are installed at: C:\skybowBackgroundAutomation\Services

Installation steps:

  1. Run the PowerShell deployment script (install_ba.ps1): 
    Launch Windows PowerShell 5.x -> "Run as Administrator" (NOT PowerShell Core). 
    Navigate to the folder containing install_ba.ps1 and run the script:
    > cd "path to folder that contains install_ba.ps1"
    > .\install_ba.ps1

  2. Follow on-screen prompts to complete the deployment.

  3. Provide user credentials.
    During the first installation, you will be prompted to provide credentials. This account will be used as:
    - Application Pool identity for the IIS site
    - Log On account for Windows services

  4. Configure URLs for IIS site.
    Open IIS Manager -> Sites -> skybow Background Automation. In the Actions panel, click 'Bindings...' and add/edit site bindings:
    - HTTP (optional): 
           - Type: http
           - IP address: All Unassigned (or specific IP)
           - Port: 9802
           - Host name: (optional)
    - HTTPS (strongly recommended):
            - Type: https
           - IP address: All Unassigned (or specific IP)
           - Port: 443
           - Host name: (optional, e.g., your public domain)
           - SSL certificate: Select a valid certificate trusted by SharePoint servers and clients
     - Click OK to save bindings.
    NOTE: SharePoint web front-end (WFE) servers must be able to reach the HTTPS URL.

  5. Update the IIS web.config file:
    Open C:\inetpub\wwwroot\skybowBackgroundAutomation\web.config and set the following keys:

    • DefaultConnection - this is connection string to SQL database. 
      - Example with Windows Authentication: 
         "Data Source=ServerName\SqlDbInstanceName;Initial Catalog=skybow.Notifications;Integrated Security=True"
      - Example with SQL Authentication:
         "Data Source=ServerName\InstanceName;Initial Catalog=skybow.BackgroundAutomation;User ID=sqluser;Password=sqlpassword"
      NOTE: If no SQL credentials are specified and Integrated Security=True is used, the IIS application pool identity (for web.config) or the Windows service Log On account (for *.exe.config) will be used to connect to SQL.

    • WebHookEndPoint / ReceverEndPoint - Public URLs for SharePoint to communicate with the IIS site.
      These URLs must be accessible from SharePoint WFE servers and must start with the public base URL of your IIS site. Example: 
      <add key="WebHookEndPoint" value="https://baservice:9802/api/webhooks/subscribe" />
      <add key="ReceiverEndPoint" value="https://baservice:9802/Services/RemoteEventReciever.svc" />

    • HttpTriggerEndPoint  - Public URL format to call Triggered Actions with HTTP request trigger type
      These URL must be accessible from SharePoint WFE servers and must start with the public base URL of your IIS site.  Example:
      <add key="HttpTriggerEndPoint" value="https://your-ba-service-url/api/trigger/{referenceId}/invoke?code={apiKey}" /> your IIS site.

  6. Start the IIS site
    On first load, the system will connect to the SQL Server and automatically create the "skybow.BackgroundAutomation" database.

  7. Update skybow.***.exe.config files for all skybow Windows services:
    -  Navigate to   "C:\skybowBackgroundAutomation\Services\". 
    - Update the *.exe.config files for the following skybow services:
                  - DefaultConnection
                  - WebHookEndPoint
                  - ReceiverEndPoint 
                  - HTTPTriggerEndPoint
    - These values should match the ones used in web.config of the IIS site (Step 5).

  8. Optional: Configure Email Notifications (SMTP):  skybow Background Automation can send automatic email notifications if background calculations or actions are disabled due to continuous execution errors.
    To enable notifications, configure the following settings in:
           - IIS web.config file:
               C:\inetpub\wwwroot\skybowBackgroundAutomation\web.config
           - ALL FIVE Windows service *.exe.config files:
               C:\skybowBackgroundAutomation\Services\
    Configuration details:
           - SmtpServerHost - SMTP server hostname.
           - SmtpServerPort - SMTP server port (587 recommended for TLS).
           - SmtpServerUserName / SmtpServerPassword - SMTP authentication credentials.
           - SmtpFromAddress - Sender email address used for notifications.
           - SmtpFromDisplayName - Display name shown in outgoing emails.
           - MaintainerEmail -  Email address that receives notifications if a background calculation 
             or triggered/scheduled action is disabled due to repeated errors
    For an SMTP server without authentication or without TLS (for example an internal relay), leave SmtpServerUserName and SmtpServerPassword empty and add the standard .NET mail settings inside <configuration> of the same files instead:
                 <system.net>
                   <mailSettings>
                     <smtp deliveryMethod="Network" from="automation@contoso.com">
                       <network host="mail.contoso.local" port="25" enableSsl="false" defaultCredentials="false" />
                     </smtp>
                   </mailSettings>
                 </system.net>
             "from" is then the sender of the error notifications.
           defaultCredentials="true" signs in to the SMTP server as the service account (Windows authentication).

    NOTE: Port 465 (implicit SSL) is not supported - use 587 (STARTTLS) or 25.

    NOTE: This configuration is optional. If not configured, background processing will continue normally, but no email notifications will be sent.

    "Send email" action for triggered and scheduled actions: The "Send email" action sends emails, including attachments, to any recipient - also outside your organization - through the SMTP server configured above. It is offered only when a sender is configured.
    Configure the following setting in:
           - IIS web.config file (makes the action available in the Background Services configuration dialog)
           - the *.exe.config files of the skybow Actions Job, skybow Scheduled Actions Job and
             skybow HTTP Trigger Job services (used when the emails are sent)
    Configuration details:
           - SendMailAction:Smtp:EmailFrom - Sender email address, optionally with a display name.
             Leave it empty to disable the action. Examples:
                                        <add key="SendMailAction:Smtp:EmailFrom" value="automation@contoso.com" />
          <add key="SendMailAction:Smtp:EmailFrom" value="Contoso Automation &lt;automation@contoso.com&gt;" />
    NOTE: Requires the SMTP server settings from "Error notifications" above (SmtpServerHost, SmtpServerPort,
             SmtpServerUserName, SmtpServerPassword - or the <system.net> mail settings).
             SmtpFromAddress, SmtpFromDisplayName and MaintainerEmail are not used by this action.
    NOTE: Attachments are limited to 25 MB in total; the SMTP server may allow less.
             The SMTP server must accept emails from this server for external recipients (relay).
    NOTE: After changing web.config, click Refresh in the Background Services configuration dialog.

  9. Restart all skybow services:
    - Press Win + R → type: services.msc
    - Locate and restart each of the following:
    1. skybow Scheduled Actions Job
    2. skybow Queue Message Job
    3. skybow Actions Job
    4. skybow CleanUp Job
    5. skybow HTTP Trigger Job

  10. Verify message queues (MSMQ). During the first start, the skybow services automatically create the required private queues in Microsoft Message Queuing. 
    Verify private queues in Computer Management -> Services and Applications -> Message Queuing -> Private Queues.
    If not created automatically, create manually (If the skybow service account does not have permission to create them, you must manually create the following queues under Private Queues): 
           - skybowssnotificationsqueue
           - skybowssscheduledactionsqueue
    Ensure the skybow service account has "Send", "Receive", and "Peek" permissions.

  11. SharePoint farm configuration (REQUIRED - run once per farm)
    Run configure_sharepoint.ps1 on the SharePoint web front-end server where skybow Background Automation is installed - elevated, as a farm administrator, in Windows PowerShell 5.1 (PowerShell 7 cannot load the SharePoint snap-in). SharePoint must be served over HTTPS.

         .\configure_sharepoint.ps1

    No arguments are needed: it reads the site collection from the farm, and the skybow service identity and configuration file locations from the skybow installation on this machine.
    From the August 2026 update for SharePoint Subscription Edition, SharePoint refuses to register event receivers for a caller that has no application identity, whatever permissions that caller holds. Without this step, newly created triggered actions and calculations fail with "Access denied".
    The script lists what it will change and asks for confirmation first, then creates that identity for the whole farm, updates the skybow configuration files and restarts skybow. Afterwards, run "iisreset" on the farm's other SharePoint servers - the script lists them by name. It covers every site collection on the farm, including ones created later, so  there is nothing to repeat when you add one.

    RENEWING THE CERTIFICATE
    The certificate the script creates is valid for five years, and the script prints its expiry date when it finishes. Before that date, run the script again on the same server, then "iisreset" on every SharePoint server: within 90 days of expiry it replaces the certificate and keeps the same application id. Running it earlier changes nothing. Add   -RenewCertificate to replace the certificate sooner.

     NOTE: the identity is granted Full Control over all content on the farm, and can act without a signed-in user. That is what skybow needs to register event receivers on the lists your automations use, and it is the configuration this release was tested with. Passing -Right Manage narrows it, but whether SharePoint accepts an event receiver registration under Manage has not been established - so treat that as untested rather than as the safer choice.

    NOTE: it also allows SharePoint to call intranet addresses, which SharePoint list webhooks require. That relaxes a farm-wide protection against server-side request forgery: it applies to the whole farm, cannot be limited to skybow, and has no allow-list. The script prints how to restore it.

    NOTE: from the September 2026 update for SharePoint Subscription Edition, SharePoint only calls back addresses that are on a farm allow-list, and otherwise refuses to register the event receiver or list webhook with "The remote event receiver URL is not allowed". The script adds the host and port from ReceiverEndPoint and WebHookEndPoint.
     

  12. SharePoint Integration (SPFx Add-in). The final step is to deploy the skybow Background Services SharePoint Framework (SPFx) add-in.
    1) Locate the Addin folder in the deployment package. It contains the following options:
        - skybow CDN (recommended). Contains packages: 
           - skybow-background-services-2019.sppkg (for SharePoint Server 2019)
           - skybow-background-services-SE.sppkg (for SharePoint Subscription Edition)
           Select the package that matches your SharePoint version. Upload and deploy the selected .sppkg file to the SharePoint App Catalog.
        - Local SharePoint Version
          Use this option if external CDN access is restricted or offline deployment is required.
                  - Follow the instructions in Addin/Local SharePoint Version/readme.txt
                 - After completing those steps, upload and deploy the corresponding .sppkg file to the SharePoint App Catalog.
    2) Add the app to the target SharePoint site.
    3) Open any list or document library on that site and click "skybow Background Services" in the command bar. 
    4) Configure the Service URL: If the background service URL has not been set for the site collection, the Configure Background Automation Service URL dialog will open automatically.
    5) In the dialog:
         - Enter the public URL of the skybow Background Automation IIS site
         - Click the Check button
         - Once the "Success" message appears, click Apply to save the configuration.

13. Validate Background Automation Service URL: When you open the Skybow Background Services dialog for the first time at the site collection level, you will be prompted to enter the Background Automation Service URL and click the “Check” button. After clicking "Check", the system validates that:
                    - The web application has access to the current site collection.
                    - The service can successfully connect to the SQL database.

     If the URL is valid, a confirmation message will appear indicating that the connection was successful and the Background Automation Service is ready to use.

NOTE1: Configure Background Automation Service URL only needs to be performed once per site collection.

NOTE 2: During future deployments, the configs will automatically back up and merge your current web.config and service *.exe.config files to preserve your configuration changes.

NOTE 3: Each time there is a change in Background Automation service you need to re-run the script.

 

Related articles