FEAT: Add conda packaging recipes and publish tooling for mssql-python

[Jahnvi Thakkar (jahnvi480)]

Work Item / Issue Reference

AB#47315

---

Summary

Adds the conda packaging foundation for mssql-python so it can be published to the
Microsoft-owned microsoft Anaconda channel alongside the existing PyPI wheels.

This is prototype / foundational tooling. The publish stage is a DRAFT and is not
wired into the official release pipeline yet — it activates only after the microsoft
channel onboarding and an org-scoped Anaconda token are provisioned. The recipes and the
local harness build and validate 100% of the mechanics offline today.

What's included

• conda/mssql-python/meta.yaml — recipe for the Python binding. Repackages the signed
  wheel (no compilation); version-locked to the mssql-python-odbc companion.
• conda/mssql-python-odbc/meta.yaml — recipe for the proprietary Microsoft ODBC Driver 18
  companion. It must live on the Microsoft-owned microsoft channel, never conda-forge.
• conda/build_and_test_local.ps1 — offline "test-before-live" harness: builds both
  packages, assembles a local channel, installs into a clean env, and runs import +
  optional live-connect smoke tests. Needs no channel onboarding or permissions.
• conda/onebranch-publish-conda-stage.yml — DRAFT OneBranch stage that builds from the
  signed release artifacts, gates on the smoke test, then publishes both packages together,
  version-locked.

Dependency hygiene

Azure SDK dependencies (azure-core / azure-identity / msal) resolve from the lean
microsoft channel under --strict-channel-priority. This deliberately avoids
conda-forge's azure-core recipe, which over-declares flask and six as runtime deps
and cascades in celery / boto3 / botocore (~30 extra packages, empirically verified
71 -> 42 packages when using the microsoft channel). The upstream fix is filed at
conda-forge/azure-core-feedstock#71.

Refs #563

[Copilot]

Pull request overview

This PR adds initial conda packaging assets for mssql-python (and its mssql-python-odbc companion) so the project can be published to the Microsoft-owned microsoft Anaconda channel, alongside the existing PyPI wheel distribution.

Changes:

• Adds conda recipes for mssql-python and mssql-python-odbc that repackage existing wheels (no compilation).
• Adds a local PowerShell harness to build both recipes, create a local channel, and validate import / optional live-connect.
• Adds a draft OneBranch stage to build/test/publish conda artifacts from signed release artifacts.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 6 comments.

File	Description
conda/onebranch-publish-conda-stage.yml	Draft OneBranch stage to build from signed artifacts, gate on smoke tests, and publish to the microsoft Anaconda channel.
conda/mssql-python/meta.yaml	Conda recipe for repackaging the mssql-python wheel and depending on a version-locked mssql-python-odbc.
conda/mssql-python-odbc/meta.yaml	Conda recipe for repackaging the proprietary driver wheel into a companion conda package.
conda/build_and_test_local.ps1	Local “test-before-live” harness to build, index, install, and smoke test the conda packages.

Suppressed comments (1)

conda/onebranch-publish-conda-stage.yml:133

• Same string-vs-boolean condition issue here: quoting the template expression turns it into a string, which can cause the publish step to be skipped unexpectedly even when publishToConda is true.

 - task: PowerShell@2
displayName: 'Publish to anaconda.org/microsoft'
condition: and(succeeded(), eq('${{ parameters.publishToConda }}', true))

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.