Word Automation Services for SharePoint 2013


Word Automation Service is a service provided by Microsoft in SharePoint 2013 to perform conversion of documents that are supported by Microsoft Word. The conversion that happens is purely server-side conversion. This service existed in SharePoint 2010 version as well. The main change in this service from SharePoint 2010 to SharePoint 2013 version is the implementation of requests for “on demand” file conversion.


In SharePoint 2010, whenever the conversion request was sent to the server it was required to create a file conversion job and by using “Start” method, the conversion job would be started. Then the conversion would actually happen based on the interval set in the properties of the Word Automation service in Central Administration. The properties in the Automation Service can also be used to set how often the timer job needs to run and how sooner it needs to start with the minimum value being one minute.

Current Scenario

In SharePoint 2013, Microsoft has maintained the earlier 2010 feature and also added “on demand” conversion to easy the burden on the developers. This feature will enable the request to be executed as soon as the request is created. Think of “on demand” as a synchronized process wherein the job is executed without any delays. Whereas, the other way is an asynchronous process which waits for some amount of time specified in the properties.

In SharePoint 2010, it was possible to convert only those documents which were present in SharePoint library. In SharePoint 2013 the conversion job can also convert the documents present in the file system using file streams. Since the file stream uses Word Automation Service, it can convert only one document at a time.


The above figure shows the architecture and the request processing method of the Word automation process from the server object model. The Word automation process maintains two queues for both kinds of processes. One queue for the “on demand” or immediate requests and the other is for SharePoint timer-job based requests. The document conversion request of “on demand”     will always get prioritized over the timer-job based requests.

If the Word automation service is already working on the timer-job based request and it receives an “on demand” request then it will immediately stop the earlier conversion job and execute the “on demand” request first.


  1. Open Central Administration and click on Manage Service Applications.
  2. In the service application list on the top ribbon click on “new” and click on “Word Automation Services”.

3.  A modal dialog box will open up as show below:

4.  Fill in the details as described below:

    1. Name – Name of the word Service example – TrigentAutomationService
    2. Application Pool Name – Preferably same as the name of the service example – TrigentAutomationService
    3. Select the security account that has been registered
    4. Partitioned Mode – No need to check this as there is no requirement of partition
    5. Add to Default Proxy List – check this – This will create word service in the proxy list
    6. Click on “Next”

5.  On click of “Next” you will be asked to give the database server and the name of the database where the service resides. It is advisable to give the same server as the Sharepoint DB

6.  Click on “Finish”. The Word Automation Service should get created successfully. It may take some time depending on the response of the system. It will be listed along with the other services as below:


Once the service is created successfully we need to modify the properties depending upon the requirement.

  1. Supported File Formats – This is used to specify what all file types can be opened by the service.
  2. Embedded Font Support – A user can choose to embed fonts within the document.
  3. Maximum Memory Usage – Maximum percentage of memory that can be used by the service from 1 to 100.
  4. Recycle Threshold – Number of documents converted by a conversion process before it is restarted.
  5. Word 97-2003 Document Scanning – Extra checks are performed before these documents are opened.
  6. Conversion Processes – The number of conversions that can be performed simultaneously.
  7. Conversion Throughput – The frequency with which groups of conversions are started in minutes.
  8. Job Monitoring – The length of time before conversions are monitored in minutes.
  9. Maximum Conversion Attempts – Maximum attempts before it is considered as failed
  10. Maximum Synchronous Conversion Requests – Maximum number of synchronous conversion requests that can be processed at a time for a server.

Business use cases

While Word Automation Service does the job of converting documents from one format to another it certainly does have multiple business uses such as –

  • An application where in the users inputs certain information and that information gets saved in a SharePoint list or library. A background code can be written to gather the user input information and create a word document. This document in turn can be used by the word automation service to convert it from word to PDF so that the document could be shared offline. This application could be as simple as generating a ticket or as complex as generating health and safety plan for any construction companies. It can have multiple input screens and multiple lists as well.
  • An application which allows the user to upload their word files with the relevant inputs and stored in a location. Word Automation Service can be used to convert these files into PDF or XPS format. It can be made to be downloaded by the user for printing or using it offline.
  • An application where based on user inputs certain pre-selected documents should attached from a source outside of SharePoint. Word Automation Service can be used to select that document and convert it and made available to the user for download.

Hybrid in SharePoint 2016

Most of us who work on Microsoft SharePoint can safely agree that Microsoft is pushing its customer base towards SharePoint online. However, the fact is,  as long as the demand for on-premise version of SharePoint continues to exist, it is likely that they will  not stop the release of the on-premise version. For most companies using on-premise SharePoint, the major focus is to work with content management features with Office 365 capabilities.

Microsoft’s vision for cloud inspired experiences for SharePoint is to extend capabilities of its on-premise and online into a connected hybrid experience.  Office 365 provides features that are beyond SharePoint’s storage facilities. Sync with One-drive for business to email storage, it gives ready-to-use user experiences. So, it is becoming inevitable to have a version which will have both the features and capabilities of SharePoint and Office 365.

What exactly is `Hybrid’?

To put it in simple words, a hybrid SharePoint environment is integration between the on-premise SharePoint server and the Office 365 environment. This will help companies to take their first step forward to experience cloud-based functionalities. A hybrid environment will help users to get started on a cloud environment  and connect to their respective content/resources whenever the same is required. This will enable users to have a more seamless user experience in terms of the two environments. The end user is not really bothered where his contents reside in SharePoint as long as it is safe and cannot be  tampered with. With this hybrid feature, search results can be consolidated between SharePoint and Office 365.

Overview of Hybrid Integration

  • Search Feature – Once the Hybrid Search is configured in the SharePoint environment, the search results from SharePoint on-premise and Office 365 will be combined and shown. Searching documents across both the platforms will be easier and quicker compared to earlier SharePoint version where this option was not available. Hybrid Search can be configured to have SharePoint online users to query and search the contents present in the SharePoint server. In the same way, SharePoint on-premise users can search and query their content, present on Sharepoint online and also search and query in Office 365 and SharePoint on-premise.
  • App Launchers – The App launcher feature that was in SharePoint online and Office 365 has been introduced in SharePoint on-Premise to enable users to have a seamless user experience when moving from one version to another. Once this feature is enabled, users can easily view the Office 365 apps such as Delve, video apps and so on in the SharePoint server app launcher. The Hybrid app launcher will have the same look and feel and reduce users to either bookmark or search for the links to navigation from SharePoint to Office 365 apps.
  • User Profiles – User profile information will be stored in both SharePoint server and Office 365. When a user wants to edit or view his information that user will be redirected to his profile in Office 365. This will enable users to have to his information in one place. These users will be called Hybrid users and their profiles as Hybrid profiles.
  •  Following Sites – Following sites and pages in the SharePoint server and online version have been consolidated and will be displayed in the same place. This will help uses to navigate to sites that are followed on both versions with ease.
  • OneDrive – Links to OneDrive have been provided to enable users to see the contents of the drive folder and share their contents present in OneDrive for Business in SharePoint server.
Exit mobile version