Fix description of Azure SQL support
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 74/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- azure, sql
- Domain
- databases, documentation
Research direction
Open the linked Microsoft SQL Server tutorial and locate the note about Azure Active Directory authentication. Compare the note with the authentication types described in the issue, then update the wording to distinguish unsupported interactive MFA from supported methods and reflect the Microsoft Entra name change; done when the page is accurate without implying that all Azure authentication is unavailable.
Written by the indexing model from the issue text.
Description
Link to doc page in question (if any):
https://docs.streamlit.io/develop/tutorials/databases/mssql#add-pyodbc-to-your-requirements-file
Name of the Streamlit feature whose docs need improvement:
Ability to connect to Microsoft SQL Server
What you think the docs should say:
There's currently a note on the docs stating that "At this time, Streamlit Community Cloud does not support Azure Active Directory authentication". This isn't accurate. There are multiple ways of authenticating to a SQL Server database using Azure Active Directory/Microsoft Entra* and some of them are possible in Community Cloud. You may want to reflect this so that people aren't put off by thinking it's not possible :)
I think what the docs might want to say is that the Azure Active Directory/Microsoft EntraActiveDirectoryInteractive authentication type isn't possible. This is the version that uses MFA, and there's no way for Community Cloud to serve a MFA pop-up. Some other authencation types do work. I can confirm that ActiveDirectoryServicePrincipal authentication works. I suspect ActiveDirectoryPassword authentication will also work, and possibly some of the other authentication types, but don't have a way of testing this.
*Microsoft renamed Azure Active Directory as Microsoft Entra in April 2024 (though for now at least the authentication types still follows the old naming). The docs may also want to reflect this name change.
- Dominant language
- JavaScript
- Stars
- 178
- Forks
- 705
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 39
Contributor guide
No contributing guide indexed for this repository
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.
More from streamlit/docs
-
docs needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
-
docs
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
docs needs triage
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
bug needs triage
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
docs needs triage
Difficulty 3/5 1-2 days Newbie friendliness 48/100
Similar issues
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100