---
schema_version: "1"
id: 66ab2dcc89c6997d52d625d4372748b7e89ab6462537c00005e1cc2b8042db75
title: Configure Azure Active Directory Authentication for MS SQL Server using the Database Connector
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/db-connector/latest/database-connector-integratedsecurity.md
canonical_url: https://docs.mulesoft.com/db-connector/latest/database-connector-integratedsecurity
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 35635e6102f930125aaf6f7061d2abd984d68b6c9f3aaa614650b73aae85251a
description: MuleSoft Documentation Site
release: "1.16"
latest: true
---
---
product: Database Connector
version: 1.16
is-latest-version: true
---

# Configure Azure Active Directory Authentication for MS SQL Server using the Database Connector

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Anypoint Connector for Database (Database Connector) enables you to configure Azure Active Directory
Authentication for MS SQL Server by setting the `IntegratedSecurity` value in the connection
configuration. The following example shows how to configure this value in Anypoint Studio:

1.  In Studio, navigate to the **Global Elements** tab.

2.  Click **Create**.

3.  In the filter box, search `database`.

4.  Select **Database Config**.

5.  Click **OK**.

6.  In the **Database Config** window, for **Connection**, select **MS SQL Server Connection**.

7.  In the **Advanced** tab, set **Connection properties** to **Edit inline**.

8.  Click the green plus sign.

9.  Set **Key** to `Integratedsecurity`.

10. Set **Value** to `true`.

11. Click **Finish**.

12. Complete the remaining connection settings for the database.

13. Click **OK**.

![Integratedsecurity key configuration in Anypoint Studio](/mulesoft/current/en-us/db-connector/latest/_images/database-connector-integrated.png)

In the **Configuration XML** editor, the `key="integratedsecurity` configuration looks like this:

```xml
<db:config name="Database_Config1" doc:name="Database Config" >
		<db:my-sql-connection >
			<db:connection-properties >
				<db:connection-property key="integratedsecurity" value="true" />
			</db:connection-properties>
		</db:my-sql-connection>
	</db:config>
```

## Windows Authentication Limitations on CloudHub and Runtime Fabric

Windows Authentication (Integrated Security or NTLM) for MS SQL Server is generally not supported,
or is highly impractical, for Mule applications deployed to Linux-based environments such as
CloudHub 1.0, CloudHub 2.0, and Runtime Fabric. These environments can’t be joined to a Windows
domain.

For these environments, use one of these options:

- SQL Server authentication (recommended)

  Connect with a SQL Server login and password.

- Kerberos authentication

  Use this option if your organization requires integrated authentication. See
  [Kerberos authentication to Microsoft SQL Server from Mule 4 apps hosted in CloudHub or RTF](https://help.salesforce.com/s/articleView?id=001116985&type=1).

> [!IMPORTANT] In CloudHub 2.0 and Runtime Fabric, the Microsoft SQL Server JDBC driver attempts
> Windows Authentication whenever the user name is in domain format, such as `DOMAIN\user`, even if
> `IntegratedSecurity=true` isn’t set. This authentication attempt fails.

## See Also

- [Database Connector Reference](https://docs.mulesoft.com/db-connector/latest/database-documentation)

- [Salesforce Help](https://help.salesforce.com)