Bernie White

### Your suggestion These are enhancements to the logging experience for debugging across PSRule emitters. ### Alternatives na ### Additional context _No response_

### Your suggestion These are enhancements to the logging experience for debugging rules. ### Alternatives na ### Additional context _No response_

### Your suggestion These are enhancements to the logging experience for debugging across PSRule core engine and any infrastructure and options required to support extensibility and rule diagnostics. ### Alternatives...

### Your suggestion Add support for copilot to be able to call PSRule scans. ### Alternatives n/a ### Additional context _No response_

### Your suggestion Single file scans should report found issues in code similar to task execution instead of only results to log. ### Alternatives n/a ### Additional context _No response_

### Your suggestion If options change the language server currently persists them until it is reloaded. The language server should automatically reload options. for example, if a convention is added...

Currently the Log Analytics workspace id and key must be provided. Using a Managed Identity to retrieve this information would be even better. [Reference](https://docs.microsoft.com/en-us/azure/active-directory/managed-identities-azure-resources/how-to-use-vm-token#get-a-token-using-http) [Identity readme](https://docs.microsoft.com/en-us/dotnet/api/overview/azure/identity-readme)

Currently PSRule for Azure Monitor uses the preview Data Collector API. A new option is available that supports Azure AD identities, using DCR-based custom log collection. This will support microsoft/PSRule#2837...

Consolidate functionality of PSRule.Monitor into PSRule repository.

Migrate contents from PSRule.Rules.MSFT.OSS into this repository and update build pipelines to consolidate the repositories to reduce maintenance and spread of issues.