df_to_azure 2.0.0__tar.gz

df_to_azure-2.0.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

df_to_azure-2.0.0/PKG-INFO

@@ -0,0 +1,224 @@
+Metadata-Version: 2.4
+Name: df_to_azure
+Version: 2.0.0
+Summary: Automatically write pandas DataFrames to SQL by creating pipelines in Azure Data Factory with copy activity from blob to SQL
+Author-email: Zypp <hello@zypp.io>
+Project-URL: Bug Tracker, https://github.com/zypp-io/df_to_azure/issues
+Project-URL: Source, https://github.com/zypp-io/df_to_azure
+Keywords: python,azure,data-warehouse,sql,blob
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: OS Independent
+Requires-Python: <3.14,>=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: azure-identity>=1.12.0
+Requires-Dist: azure-mgmt-datafactory>=7.1.0
+Requires-Dist: azure-mgmt-resource>=23.1.1
+Requires-Dist: azure-storage-blob>=12.20.0
+Requires-Dist: pandas>=2.2.2
+Requires-Dist: pyarrow>=16.1.0
+Requires-Dist: pyodbc>=5.1.0
+Requires-Dist: sqlalchemy>=2.0.36
+Dynamic: license-file
+
+DF to Azure
+===
+
+[![Downloads](https://pepy.tech/badge/df_to_azure)](https://pepy.tech/project/keyvault)
+[![Open Source](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://opensource.org/)
+[![Code style: black](https://img.shields.io/badge/code%20style-black-000000.svg)](https://github.com/psf/black)
+[![PyPI](https://img.shields.io/pypi/v/df_to_azure)](https://pypi.org/project/df-to-azure/)
+[![Latest release](https://badgen.net/github/release/zypp-io/df_to_azure)](https://github.com/zypp-io/df_to_azure/releases)
+
+> Python module for fast upload of pandas DataFrame to Azure SQL Database using automatic created pipelines in Azure Data Factory.
+
+Supported Python versions: 3.11, 3.12, and 3.13.
+
+## Introduction
+
+The purpose of this project is to upload large datasets using Azure Data Factory combined with an Azure SQL Server.
+In steps the following process kicks off:<p>
+    1. The data will be uploaded as a .csv file to Azure Blob storage.<br>
+    2. A SQL table is prepared based on [pandas DataFrame types](https://pandas.pydata.org/pandas-docs/stable/user_guide/basics.html#basics-dtypes),
+which will be converted to the corresponding [SQLAlchemy types](https://docs.sqlalchemy.org/en/14/core/type_basics.html). <br>
+    3. A pipeline is created in datafactory for uploading the .csv from the Blob storage into the SQL table.<br>
+    4. The pipeline is triggered, so that the .csv file is bulk inserted into the SQL table.<br>
+
+## How it works
+
+Based on the following attributes, it is possible to bulk insert your dataframe into the SQL Database:
+
+```python
+from df_to_azure import df_to_azure
+
+df_to_azure(df=df, tablename="table_name", schema="schema", method="create")
+```
+
+1. `df`: dataframe you wish to export
+2. `tablename`: desired name of the table
+3. `schema`: desired sql schema
+4. `method`: option for "create" "append" or "upsert"
+5. `id_field`: id field of the table. Necessary if `method` is set to "upsert"
+
+**Important**: the csv's are uploaded to a container called `dftoazure`, so create this in your storage account before using this module.
+
+##### Upsert / create or append
+It is possible to upsert the SQL table with (new) records, if present in the dataframe you want to upload.
+Based on the id_field, the SQL table is being checked on overlapping values.
+If there are new records, the "old" records will be updated in the SQL table.
+The new records will be uploaded and appended to the current SQL table.
+
+# Settings
+The default authentication path is passwordless:
+
+- Python Azure SDK clients use `DefaultAzureCredential`.
+- Local development can use `az login`.
+- Deployed Python workloads can use a managed identity.
+- Data Factory linked services use the Data Factory managed identity by default.
+
+You should not need SQL passwords, storage account keys, or storage connection strings for the default setup. When
+legacy values are present, the package uses a fixed fallback order instead of auth-mode environment variables.
+
+## Parquet
+Since version 0.6.0, functionality for uploading dataframe to parquet is supported. simply add argument `parquet=True` to upload the dataframe to the Azure storage container parquet.
+The arguments tablename and schema will be used to create a folder structure. if parquet is set to True, the dataset will not be uploaded to a SQL database.
+
+```text
+# Azure subscription and Data Factory settings
+subscription_id=""
+rg_name=""
+rg_location="westeurope"
+df_name=""
+
+# Storage account used for temporary SQL upload parquet files and parquet=True uploads.
+# Use this for passwordless storage auth. If you use a storage connection string instead,
+# ls_blob_account_name is not required.
+ls_blob_account_name=""
+
+# Azure SQL Database
+SQL_SERVER="<server-name>.database.windows.net"
+SQL_DB=""
+```
+
+The lowercase names above are the original names and remain supported. Uppercase aliases are also accepted, for example
+`SUBSCRIPTION_ID`, `RG_NAME`, `RG_LOCATION`, `DF_NAME`, `LS_BLOB_ACCOUNT_NAME`, and `LS_BLOB_ACCOUNT_KEY`.
+
+The authentication rule is the same for direct Python connections and the Data Factory linked services:
+**explicit credentials win, and without them the package is passwordless.** To go passwordless, simply do not set the
+password, key, and connection-string variables.
+
+- Storage: `AZURE_STORAGE_CONNECTION_STRING` → `LS_BLOB_ACCOUNT_NAME` + `LS_BLOB_ACCOUNT_KEY` →
+  `LS_BLOB_ACCOUNT_NAME` with `DefaultAzureCredential` (Python) / managed identity (ADF).
+- SQL: `SQL_USER` + `SQL_PW` → passwordless: `DefaultAzureCredential` access token over ODBC (Python) /
+  managed identity (ADF).
+  The ADF SQL linked service uses the user-assigned managed identity referenced by `DF_TO_AZURE_ADF_CREDENTIAL_NAME`
+  when set, otherwise the system-assigned managed identity.
+- Azure management clients always use `DefaultAzureCredential`.
+
+For a user-assigned managed identity on Data Factory, first create a credential in the Data Factory itself
+(Manage → Credentials) that references the identity, then set the *name of that credential* — not the identity's
+client ID or resource ID:
+
+```text
+DF_TO_AZURE_ADF_CREDENTIAL_NAME=""
+```
+
+## Azure permissions for passwordless auth
+
+There are two identities involved in a normal SQL upload:
+
+1. The identity running Python.
+2. The managed identity of the Azure Data Factory that runs the copy pipeline.
+
+For local development, sign in first:
+
+```commandline
+az login
+```
+
+Grant the local developer identity:
+
+- Azure permissions to create or update Data Factory pipelines, datasets, and linked services. `Data Factory Contributor` on the Data Factory is usually enough when `create=False`; resource group `Contributor` is needed when using `create=True`.
+- `Storage Blob Data Contributor` on the storage account or the relevant containers.
+- A contained Azure SQL user and database permissions for creating schemas, tables, and upsert procedures.
+
+Example SQL permissions for the local developer or deployed Python host identity:
+
+```sql
+CREATE USER [user-or-managed-identity-name] FROM EXTERNAL PROVIDER;
+ALTER ROLE db_datareader ADD MEMBER [user-or-managed-identity-name];
+ALTER ROLE db_datawriter ADD MEMBER [user-or-managed-identity-name];
+ALTER ROLE db_ddladmin ADD MEMBER [user-or-managed-identity-name];
+```
+
+Grant the Data Factory managed identity:
+
+- `Storage Blob Data Reader` on the storage account or the `dftoazure` container so ADF can read the staged parquet file.
+- An Azure SQL contained user with permission to insert into the target and staging tables.
+- `EXECUTE` permission when using `method="upsert"` because ADF runs the generated upsert stored procedure.
+
+Example SQL permissions for the Data Factory system-assigned managed identity:
+
+```sql
+CREATE USER [your-data-factory-name] FROM EXTERNAL PROVIDER;
+ALTER ROLE db_datareader ADD MEMBER [your-data-factory-name];
+ALTER ROLE db_datawriter ADD MEMBER [your-data-factory-name];
+GRANT EXECUTE TO [your-data-factory-name];
+```
+
+Azure SQL must have a Microsoft Entra admin configured before `CREATE USER ... FROM EXTERNAL PROVIDER` works.
+
+For user-assigned managed identity on Data Factory, assign the identity to the factory, create a Data Factory credential for it, and set `DF_TO_AZURE_ADF_CREDENTIAL_NAME` to that credential name.
+
+Passwordless SQL connections require a Microsoft ODBC Driver for SQL Server version that supports access-token
+authentication. Use the newest available ODBC Driver 18 where possible.
+
+### Cross-tenant databases
+
+A Data Factory in a different subscription is fine with managed identity when it is still in the same tenant as the
+Azure SQL server. When the Data Factory and Azure SQL server are in different tenants, managed identity may not be a
+valid SQL principal in the target tenant. In that case, set `SQL_USER` and `SQL_PW`; the package will use those
+credentials for both direct Python SQL setup and the ADF SQL linked service. No extra auth-mode variables are required.
+
+## Maintained by [Zypp](https://github.com/zypp-io):
+- [Melvin Folkers](https://github.com/melvinfolkers)
+- [Erfan Nariman](https://github.com/erfannariman)
+
+## Support:
+For support on using this module, you can reach us at [hello@zypp.io](mailto:hello@zypp.io)
+
+---
+
+## Testing
+
+The auth tests are unit tests and run without any Azure resources or environment variables:
+
+```commandline
+pytest df_to_azure/tests/test_auth.py
+```
+
+The rest of the test suite are integration tests: they create real pipelines, blob containers, and SQL tables in
+Azure. To run them, point the environment variables from the [Settings](#settings) section at an Azure environment
+you own:
+
+```text
+SUBSCRIPTION_ID=""
+RG_NAME=""
+RG_LOCATION="westeurope"
+DF_NAME=""
+LS_BLOB_ACCOUNT_NAME=""
+SQL_SERVER="<server-name>.database.windows.net"
+SQL_DB=""
+```
+
+Authenticate (for example with `az login`, see the permissions section above), then run:
+
+```commandline
+pytest df_to_azure
+```
+
+Tip: put the variables in a local `.env` file (git-ignored) and run `uv run --env-file .env pytest df_to_azure`.

df_to_azure-2.0.0/README.md

@@ -0,0 +1,197 @@
+DF to Azure
+===
+
+[![Downloads](https://pepy.tech/badge/df_to_azure)](https://pepy.tech/project/keyvault)
+[![Open Source](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://opensource.org/)
+[![Code style: black](https://img.shields.io/badge/code%20style-black-000000.svg)](https://github.com/psf/black)
+[![PyPI](https://img.shields.io/pypi/v/df_to_azure)](https://pypi.org/project/df-to-azure/)
+[![Latest release](https://badgen.net/github/release/zypp-io/df_to_azure)](https://github.com/zypp-io/df_to_azure/releases)
+
+> Python module for fast upload of pandas DataFrame to Azure SQL Database using automatic created pipelines in Azure Data Factory.
+
+Supported Python versions: 3.11, 3.12, and 3.13.
+
+## Introduction
+
+The purpose of this project is to upload large datasets using Azure Data Factory combined with an Azure SQL Server.
+In steps the following process kicks off:<p>
+    1. The data will be uploaded as a .csv file to Azure Blob storage.<br>
+    2. A SQL table is prepared based on [pandas DataFrame types](https://pandas.pydata.org/pandas-docs/stable/user_guide/basics.html#basics-dtypes),
+which will be converted to the corresponding [SQLAlchemy types](https://docs.sqlalchemy.org/en/14/core/type_basics.html). <br>
+    3. A pipeline is created in datafactory for uploading the .csv from the Blob storage into the SQL table.<br>
+    4. The pipeline is triggered, so that the .csv file is bulk inserted into the SQL table.<br>
+
+## How it works
+
+Based on the following attributes, it is possible to bulk insert your dataframe into the SQL Database:
+
+```python
+from df_to_azure import df_to_azure
+
+df_to_azure(df=df, tablename="table_name", schema="schema", method="create")
+```
+
+1. `df`: dataframe you wish to export
+2. `tablename`: desired name of the table
+3. `schema`: desired sql schema
+4. `method`: option for "create" "append" or "upsert"
+5. `id_field`: id field of the table. Necessary if `method` is set to "upsert"
+
+**Important**: the csv's are uploaded to a container called `dftoazure`, so create this in your storage account before using this module.
+
+##### Upsert / create or append
+It is possible to upsert the SQL table with (new) records, if present in the dataframe you want to upload.
+Based on the id_field, the SQL table is being checked on overlapping values.
+If there are new records, the "old" records will be updated in the SQL table.
+The new records will be uploaded and appended to the current SQL table.
+
+# Settings
+The default authentication path is passwordless:
+
+- Python Azure SDK clients use `DefaultAzureCredential`.
+- Local development can use `az login`.
+- Deployed Python workloads can use a managed identity.
+- Data Factory linked services use the Data Factory managed identity by default.
+
+You should not need SQL passwords, storage account keys, or storage connection strings for the default setup. When
+legacy values are present, the package uses a fixed fallback order instead of auth-mode environment variables.
+
+## Parquet
+Since version 0.6.0, functionality for uploading dataframe to parquet is supported. simply add argument `parquet=True` to upload the dataframe to the Azure storage container parquet.
+The arguments tablename and schema will be used to create a folder structure. if parquet is set to True, the dataset will not be uploaded to a SQL database.
+
+```text
+# Azure subscription and Data Factory settings
+subscription_id=""
+rg_name=""
+rg_location="westeurope"
+df_name=""
+
+# Storage account used for temporary SQL upload parquet files and parquet=True uploads.
+# Use this for passwordless storage auth. If you use a storage connection string instead,
+# ls_blob_account_name is not required.
+ls_blob_account_name=""
+
+# Azure SQL Database
+SQL_SERVER="<server-name>.database.windows.net"
+SQL_DB=""
+```
+
+The lowercase names above are the original names and remain supported. Uppercase aliases are also accepted, for example
+`SUBSCRIPTION_ID`, `RG_NAME`, `RG_LOCATION`, `DF_NAME`, `LS_BLOB_ACCOUNT_NAME`, and `LS_BLOB_ACCOUNT_KEY`.
+
+The authentication rule is the same for direct Python connections and the Data Factory linked services:
+**explicit credentials win, and without them the package is passwordless.** To go passwordless, simply do not set the
+password, key, and connection-string variables.
+
+- Storage: `AZURE_STORAGE_CONNECTION_STRING` → `LS_BLOB_ACCOUNT_NAME` + `LS_BLOB_ACCOUNT_KEY` →
+  `LS_BLOB_ACCOUNT_NAME` with `DefaultAzureCredential` (Python) / managed identity (ADF).
+- SQL: `SQL_USER` + `SQL_PW` → passwordless: `DefaultAzureCredential` access token over ODBC (Python) /
+  managed identity (ADF).
+  The ADF SQL linked service uses the user-assigned managed identity referenced by `DF_TO_AZURE_ADF_CREDENTIAL_NAME`
+  when set, otherwise the system-assigned managed identity.
+- Azure management clients always use `DefaultAzureCredential`.
+
+For a user-assigned managed identity on Data Factory, first create a credential in the Data Factory itself
+(Manage → Credentials) that references the identity, then set the *name of that credential* — not the identity's
+client ID or resource ID:
+
+```text
+DF_TO_AZURE_ADF_CREDENTIAL_NAME=""
+```
+
+## Azure permissions for passwordless auth
+
+There are two identities involved in a normal SQL upload:
+
+1. The identity running Python.
+2. The managed identity of the Azure Data Factory that runs the copy pipeline.
+
+For local development, sign in first:
+
+```commandline
+az login
+```
+
+Grant the local developer identity:
+
+- Azure permissions to create or update Data Factory pipelines, datasets, and linked services. `Data Factory Contributor` on the Data Factory is usually enough when `create=False`; resource group `Contributor` is needed when using `create=True`.
+- `Storage Blob Data Contributor` on the storage account or the relevant containers.
+- A contained Azure SQL user and database permissions for creating schemas, tables, and upsert procedures.
+
+Example SQL permissions for the local developer or deployed Python host identity:
+
+```sql
+CREATE USER [user-or-managed-identity-name] FROM EXTERNAL PROVIDER;
+ALTER ROLE db_datareader ADD MEMBER [user-or-managed-identity-name];
+ALTER ROLE db_datawriter ADD MEMBER [user-or-managed-identity-name];
+ALTER ROLE db_ddladmin ADD MEMBER [user-or-managed-identity-name];
+```
+
+Grant the Data Factory managed identity:
+
+- `Storage Blob Data Reader` on the storage account or the `dftoazure` container so ADF can read the staged parquet file.
+- An Azure SQL contained user with permission to insert into the target and staging tables.
+- `EXECUTE` permission when using `method="upsert"` because ADF runs the generated upsert stored procedure.
+
+Example SQL permissions for the Data Factory system-assigned managed identity:
+
+```sql
+CREATE USER [your-data-factory-name] FROM EXTERNAL PROVIDER;
+ALTER ROLE db_datareader ADD MEMBER [your-data-factory-name];
+ALTER ROLE db_datawriter ADD MEMBER [your-data-factory-name];
+GRANT EXECUTE TO [your-data-factory-name];
+```
+
+Azure SQL must have a Microsoft Entra admin configured before `CREATE USER ... FROM EXTERNAL PROVIDER` works.
+
+For user-assigned managed identity on Data Factory, assign the identity to the factory, create a Data Factory credential for it, and set `DF_TO_AZURE_ADF_CREDENTIAL_NAME` to that credential name.
+
+Passwordless SQL connections require a Microsoft ODBC Driver for SQL Server version that supports access-token
+authentication. Use the newest available ODBC Driver 18 where possible.
+
+### Cross-tenant databases
+
+A Data Factory in a different subscription is fine with managed identity when it is still in the same tenant as the
+Azure SQL server. When the Data Factory and Azure SQL server are in different tenants, managed identity may not be a
+valid SQL principal in the target tenant. In that case, set `SQL_USER` and `SQL_PW`; the package will use those
+credentials for both direct Python SQL setup and the ADF SQL linked service. No extra auth-mode variables are required.
+
+## Maintained by [Zypp](https://github.com/zypp-io):
+- [Melvin Folkers](https://github.com/melvinfolkers)
+- [Erfan Nariman](https://github.com/erfannariman)
+
+## Support:
+For support on using this module, you can reach us at [hello@zypp.io](mailto:hello@zypp.io)
+
+---
+
+## Testing
+
+The auth tests are unit tests and run without any Azure resources or environment variables:
+
+```commandline
+pytest df_to_azure/tests/test_auth.py
+```
+
+The rest of the test suite are integration tests: they create real pipelines, blob containers, and SQL tables in
+Azure. To run them, point the environment variables from the [Settings](#settings) section at an Azure environment
+you own:
+
+```text
+SUBSCRIPTION_ID=""
+RG_NAME=""
+RG_LOCATION="westeurope"
+DF_NAME=""
+LS_BLOB_ACCOUNT_NAME=""
+SQL_SERVER="<server-name>.database.windows.net"
+SQL_DB=""
+```
+
+Authenticate (for example with `az login`, see the permissions section above), then run:
+
+```commandline
+pytest df_to_azure
+```
+
+Tip: put the variables in a local `.env` file (git-ignored) and run `uv run --env-file .env pytest df_to_azure`.

df_to_azure-2.0.0/df_to_azure/__init__.py

@@ -0,0 +1,13 @@
+import logging
+
+from .export import df_to_azure as df_to_azure
+
+__version__ = "2.0.0"
+
+logging.basicConfig(
+    format="%(asctime)s.%(msecs)03d [%(levelname)-5s] [%(name)s] - %(message)s",
+    datefmt="%Y-%m-%d %H:%M:%S",
+    level=logging.INFO,
+)
+logging.getLogger("azure.core.pipeline.policies.http_logging_policy").setLevel(logging.WARNING)
+logging.getLogger("azure.identity._internal.get_token_mixin").setLevel(logging.WARNING)