It is recommended that you create a separate Microsoft Dynamics NAV Server instance for each NAS services application. See How to: Create a Microsoft Dynamics NAV Server Instance.

There are multiple reasons for running NAS services sessions in dedicated Microsoft Dynamics NAV Server instances:

• Efficiency and convenience
  When you change any Microsoft Dynamics NAV Server setting, you must restart the instance for the change to take effect, which interrupts all services using that instance. So if you are running different types of services in the same instance—for example, RoleTailored client services and NAS services—making a change to the settings for either service type will require a server instance restart that interrupts all other service types running through that instance.
  Even for different types of NAS services applications it’s wise to run each application in a separate server instance. For example, if you will be using NAS services for a Microsoft Office Outlook Integration application and also for a Microsoft Dynamics NAV job queue application, create a separate Microsoft Dynamics NAV Server instance for each NAS services application. This way, if you need to modify settings for the Microsoft Office Outlook Integration application you will not affect the Microsoft Dynamics NAV job queue application, and vice-versa.
  
• Performance
  Configuring NAS services applications to use separate server instances makes better use of the server computer’s resources, allowing you to run more applications with less degradation.
  
• Efficient error tracking
  If a NAS services session terminates in an error, and there are no other services running on the Microsoft Dynamics NAV Server instance, the service instance terminates and can be handled like any other Windows service. For example, you could configure the Recovery tab on the Service configuration tool in Control Panel to restart or otherwise manage the service.
  

You configure NAS services using the settings in Microsoft Dynamics NAV Server Administration tool.

Note
On the General tab, the Services Default Company specifies the default company that is used by NAS Services as well as other types of client connections.

The following settings are available on the NAS Services tab:

NAS services sessions execute in the time zone specified by the ServicesDefaultTimeZone parameter for Microsoft Dynamics NAV Server. See Configuring Microsoft Dynamics NAV Server for details on this parameter.

In multilanguage deployments of Microsoft Dynamics NAV, the language preferences and regional settings for the user account that NAS services settings runs as determine the formatting of the data. Language preferences for a user account can be set in Windows or in Microsoft Dynamics NAV. For example, in Microsoft Dynamics NAV, in the User Personalization Card window, you can specify a language for the user. But you can also set up a default language for the Microsoft Dynamics NAV deployment by creating an empty row in the User Personalization List window. If you create an entry where you specify a language but not a user ID, then NAS services will use that language unless the session runs with a user account where you have specified another language.

The following table illustrates how combinations of language personalization and regional settings impact data that a NAS services session processes. In this example, the NAS services session runs a computer where the regional settings are set to use the Spanish format. In Microsoft Dynamics NAV, the user account that the NAS services session runs as either has a language personalization or not.

Concepts