Create Microsoft Azure Access Control Service Users

Microsoft Azure Access Control service (ACS) users are one of four types of users that you can create in Microsoft Dynamics NAV clients. For more information about how to create one or more users for ACS authentication, see the "To create a new user for AccessControlService authentication" section in How to: Create Microsoft Dynamics NAV Users. Follow the instructions and make a note of the user names and authentication keys for any users that you create.

Important
If ACS authentication is not available, consider creating at least one user who will be able to connect by using a Microsoft Dynamics NAV client. For example, if users are registered by using a certain ACS namespace and that namespace changes, then the users will no longer be able to connect. One way to prevent this kind of lockout is to create a user who will be able to access the client using NavUserPassword authentication. For more information, see Users and Credential Types. Another option is to create an ACS user but to never log that user in with ACS authentication, so that the user's ACS status remains Pending. For either option, make sure that you assign the SUPER permission set to this user, to make sure that there is at least one user with full access to all client functionality.

Important

If ACS authentication is not available, consider creating at least one user who will be able to connect by using a Microsoft Dynamics NAV client. For example, if users are registered by using a certain ACS namespace and that namespace changes, then the users will no longer be able to connect.

One way to prevent this kind of lockout is to create a user who will be able to access the client using NavUserPassword authentication. For more information, see Users and Credential Types. Another option is to create an ACS user but to never log that user in with ACS authentication, so that the user's ACS status remains Pending.

For either option, make sure that you assign the SUPER permission set to this user, to make sure that there is at least one user with full access to all client functionality.