Skip to content

Update elastic query security notes in documentation #10268

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
chassq wants to merge 2 commits into
base: live
Choose a base branch
from
+2 −0
Open

Update elastic query security notes in documentation #10268

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ebae420
Update elastic query security notes in documentation
Jan 19, 2026
d9f1f34
Update azure-sql/database/elastic-query-overview.md
Jan 19, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions azure-sql/database/elastic-query-overview.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -155,6 +155,8 @@ Elastic query is included in the cost of Azure SQL Database. Topologies where yo
- Elastic query works with Azure SQL Database only. You can't use it for querying a SQL Server instance, Azure SQL Managed Instance, or Fabric SQL database.

- Private links are currently not supported with elastic query for those databases that are targets of external data sources.

- Elastic queries only support SQL logins. This presents a security problem as SQL logins are not recommneded to be used as they require passwords to be stored and securly maintained in other resources. Until elastic queries support managed identity they are not recommended from a security perspective.
Comment thread
chassq marked this conversation as resolved.
Outdated
Copy link

Copilot AI Jan 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The sentence structure needs improvement. According to the Microsoft Writing Style Guide, sentences should be concise and clear. Consider breaking this long sentence into multiple sentences or restructuring it for better readability. Additionally, avoid phrases like "security problem" - use more specific, technical language such as "security concern" or "security limitation".

Copilot uses AI. Check for mistakes.
Copy link
Copy Markdown
Author

@chassq chassq Jan 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is neither a limitation nor concern. This is a problem. Plain and simple. It opens up the uninitiated to a security problem if they do not understand the implication of using SQL Logins. Elastic queries should only support Managed identity and not support SQL logins. However since that is not currently the case the problem should be clearly called out.

Copy link

Copilot AI Jan 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Two spelling errors detected: "recommneded" should be "recommended" and "securly" should be "securely".

Suggested change
- Elastic queries only support SQL logins. This presents a security problem as SQL logins are not recommneded to be used as they require passwords to be stored and securly maintained in other resources. Until elastic queries support managed identity they are not recommended from a security perspective.
- Elastic queries only support SQL logins. This presents a security problem as SQL logins are not recommended to be used as they require passwords to be stored and securely maintained in other resources. Until elastic queries support managed identity they are not recommended from a security perspective.

Copilot uses AI. Check for mistakes.

## Related content

Expand Down
Loading