Support "Active Directory Password" authentication method for TargetSqlConnectionAuthentication

Open

#8 opened on Mar 19, 2024 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 4/5
Estimated time: 3-5 days
Newbie friendliness: 35/100

Issue type: Feature
Clarity: Mostly clear
Activity status: Stale
Tech stack: azure, powershell, sql
Domain: authentication, cloud, database

Research direction

Start by locating TargetSqlConnectionAuthentication and reviewing how its existing SqlAuthentication and WindowsAuthentication options are handled. Clarify whether the goal is Active Directory Password, managed identity, or both; done means the selected authentication method is accepted for SQL Server to Azure SQL Database migrations and works through the PowerShell flow.

Written by the indexing model from the issue text.

Description

Please provide us with the following information:

This issue is for a: (mark with an `x`)

- [ ] bug report -> please search issues before submitting
- [x ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

For "SQL Server to Azure SQL Database" with Powershell, TargetSqlConnectionAuthentication currently only supports two types: The authentication type for connection, which can be either SqlAuthentication or WindowsAuthentication.

Can it be extended to support "Active Directory Password" or managed identity?

Any log messages given by the failure

Expected/desired behavior

"Active Directory Password" or managed identity authentication methods are supported.

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)

Versions

Mention any other details that might be useful

Thanks! We'll be in touch soon.

Dominant language: PowerShell
Stars: 24
Forks: 20
PR merge metrics: No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

False positive: TurkScan.com / TurkChain network Open

blocklist removal

Difficulty 2/5 1-3 hours Newbie friendliness 65/100

MetaMask/eth-phishing-detect#296544 · Opened Sep 23, 2026
Usage of curl in mcr.microsoft.com/azure-functions/dotnet-isolated:4-dotnet-isolated10.0 Open

Difficulty 2/5 1-3 hours Newbie friendliness 70/100

Azure/azure-functions-docker#1257 · Opened Sep 23, 2026
build_ca_bundle.py: cap the privileged read size of the swapd-controlled CA Open

area:proxy bug security severity:low track:open-source

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

ntindle/spark-vm#300 · Opened Sep 23, 2026
versions endpoint passes commit_hash to git show unvalidated: option injection (read tier, root-level entries) Open

bug server

Difficulty 2/5 1-3 hours Newbie friendliness 70/100

markramm/pyrite#333 · Opened Sep 23, 2026
normalizeFilePath() leaks the username whenever the viewing OS differs from the machine the path came from Open

Difficulty 2/5 1-3 hours Newbie friendliness 70/100

bytedance/UI-TARS-desktop#2009 · 1 comment · Opened Sep 23, 2026

More Security issues