[DRAFT] Integrated Security Tests

[paulmedynski]

We seem to be skipping any tests that require Integrated Security. Our PR/CI pipelines appear to intend to use an Azure DevOps Library variable $(SupportsIntegratedSecurity), which is always true, but the tests still aren't running. I have forced this value to true in the pipelines themselves, and we will see what happens...

[Copilot]

Pull request overview

This draft PR investigates why Integrated Security tests are being skipped in the CI/CD pipeline. The author suspects that the Azure DevOps Library variable $(SupportsIntegratedSecurity) isn't being properly resolved, even though it should always be true. The PR hardcodes this value to true in the pipeline configuration to test whether this resolves the issue.

Changes:

• Hardcoded SupportsIntegratedSecurity: true in 6 test configurations that use local SQL Server instances (SQL 2019 x64, SQL 2019 x86, SQL 2022 x64, SQL 2022 x86, SQL 2022 named instance, and Always Encrypted tests)

[Copilot]

There's a spelling error in the PR title. "Seciruty" should be "Security".

[Copilot]

Hardcoding configuration values like this removes flexibility and makes it difficult to override this setting for different environments or test scenarios. While this change is appropriate for investigating why tests are being skipped, for a production solution consider:

1. Investigating why the Azure DevOps Library variable $(SupportsIntegratedSecurity) isn't being properly resolved
2. Ensuring the variable is correctly set in the 'ADO Test Configuration Properties' variable group
3. If the variable needs to always be true for these local SQL Server configurations, document this requirement

Since this is marked as a DRAFT PR for experimentation, this approach is acceptable for testing purposes, but shouldn't be merged as-is.

Suggested change

	SupportsIntegratedSecurity: true
	SupportsIntegratedSecurity: $(SupportsIntegratedSecurity)