> ## Documentation Index
> Fetch the complete documentation index at: https://docs.paradime.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Microsoft Fabric
> Integrate Microsoft Fabric with Paradime to enable dbt™ development
Microsoft Fabric is a unified analytics platform that combines data warehousing and analytics services. As a development environment in Paradime, Microsoft Fabric enables dbt™️ development from Paradime's **Code IDE**.
**IP RESTRICTIONS**
Make sure to allow traffic from one of the Paradime IPs in your firewall depending on the data location selected.
👉 See also: [Paradime IP addresses](/developers/ip-restrictions).
### Authentication Methods
Microsoft Fabric uses Microsoft Entra ID (formerly Azure AD) as its primary authentication system. Set `authentication` to one of these values:
* `ActiveDirectoryPassword` - Microsoft Entra ID username and Password
* `ServicePrincipal` - Service Principal Authentication
### Setup Instructions
1. Click **Settings** in the top menu bar of the Paradime interface to access **Account Settings**
2. In the left sidebar, click "**Connections**"
3. Click "**Add New**" next to the Code IDE section
4. Select "**Microsoft Fabric**"
5. In the **Profile Configuration** field, add the following parameters based on your authentication method. Reference the [**Profile Fields Reference**](/products/settings/connections/development-environment/microsoft-fabric#profile-fields-reference) section below for additional context and configurations:
**Microsoft Entra ID username and Password**
```yaml theme={"system"}
driver: 'ODBC Driver 18 for SQL Server' # ODBC driver name
server: fabric.analytics.com # Server hostname
port: 1433 # Default port
database: analytics_db # Database name
schema: reporting # Schema name
authentication: ActiveDirectoryPassword # Password authentication
user: user@company.com # User email
password: your_password # User password
```
**Service Principal**
**Configuration Parameters**
```yaml theme={"system"}
driver: 'ODBC Driver 18 for SQL Server' # ODBC Driver for SQL Server
server: fabric.analytics.com # Server hostname or IP address
port: 1433 # Server port number
database: analytics_db # Database name
schema: reporting # Schema name
authentication: ServicePrincipal # Authentication method
tenant_id: your_tenant_id # Microsoft Entra tenant ID
client_id: your_client_id # Application (client) ID
client_secret: your_client_secret # Client secret value
```
After adding the configuration, ensure it's properly formatted using a YAML formatter like [YAML Formatter](https://jsonformatter.org/yaml-formatter).
6. Provide a dbt™ **Profile Name** (This should match with the profile name set in your `dbt_project.yml`).
7. In the **Target** field, enter "**dev**". This is the default target your dbt project will use for development work.
8. The "**Schema**" field is pre-configured, but you can change it to specify the schema where dbt will build objects.
9. The "**Threads**" value is pre-configured to 1, but you can adjust this number to specify how many parallel operations your dbt project can run.
***
### Example Profile Configuration
***
### Schema Authorization
When creating schemas in Microsoft Fabric, you can control who owns them. Here's what you need to know:
* Schema ownership is defined using the [AUTHORIZATION Argument](https://learn.microsoft.com/en-us/sql/t-sql/statements/create-schema-transact-sql?view=sql-server-ver16#arguments). The syntax follows this pattern:
```sql theme={"system"}
CREATE SCHEMA [schema_name] AUTHORIZATION [schema_authorization]
```
* Useful for managing permissions in Microsoft Entra ID environments
* Recommended when working with group-based permissions
***
### Profile Fields Reference
| Field | Description | Example | Default | Required |
| --------------------- | ------------------------------------------------------- | ------------------------------- | ------------------------------- | -------- |
| driver | OBDC driver | `ODBC Driver 18 for SQL Server` | `ODBC Driver 18 for SQL Server` | ✅ |
| host | SQL analytics endpoint | `localhost` | None | ❌ |
| port | Server port number | `1433` | `1433` | ✅ |
| database | Database name | `analytics_db` | None | ✅ |
| schema | Schema name.This is configured in the UI "Schema" field | `dbo` | `dbo` | ✅ |
| authentication | Authentication method | `sql` | `sql` | ✅ |
| retries | Number of connections retry attempts | `1` | `1` | ❌ |
| encrypt | Enable connection encryption | `true` | `true` | ❌ |
| trust\_cert | Trust server certificate | `false` | `false` | ❌ |
| login\_timeout | Connection timeout in seconds | `0` | `0` | ❌ |
| query\_timeout | Query timeout in seconds | `0` | `0` | ❌ |
| schema\_authorization | Schema owner principal | db\_owner | None | ❌ |
| UID | Username for authentication (when required) | fabric\_user | None | ❌ |
| PWD | Password for authentication (when required) | your\_password | None | ❌ |
| tenant\_id | Microsoft Entra ID tenant ID (for service principal) | your\_tenant\_id | None | ❌ |
| client\_id | Microsoft Entra service principal client ID | your\_client\_id | None | ❌ |
| client\_secret | Microsoft Entra service principal client secret | your\_client\_secret | None | ❌ |
## Related topics
- [Microsoft Fabric](/products/settings/connections/dinoai-background-agent-environment/microsoft-fabric.md)
- [Microsoft Fabric Tools](/products/dino-ai/tools-and-features/warehouse-tool/microsoft-fabric-tools.md)
- [Scheduler environment](/products/settings/connections/scheduler-environment/index.md)
- [DinoAI Background Agent environment](/products/settings/connections/dinoai-background-agent-environment/index.md)