Skip to content
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.

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

AzureGov support #174

Closed
rpsmith310 opened this issue Jun 16, 2021 · 1 comment · Fixed by #193
Closed

AzureGov support #174

rpsmith310 opened this issue Jun 16, 2021 · 1 comment · Fixed by #193
Labels
question Further information is requested

Comments

@rpsmith310
Copy link

Hello,

Does this tool support Sentinel in AzureGov?

@ianhelle
Copy link
Contributor

Hi,
It does in theory. However, there are some caveats:

  1. You need to be able to install it and dependencies from PyPI - this might be an issue in an air-gapped environment. We have some workarounds for this using a scripted copy and install from a shared folder/URL
  2. The URL used by the KQL connection assumes the public cloud by default. You can change this in a couple of ways:
  • Set the environment variable KQLMAGIC_CONFIGURATION=cloud=government
  • After loading the Azure Sentinel query provider (but before authenticating) run this in a single cell
    %kql --config 'cloud=government'
  1. Our keyvault support (for storing/retrieving secrets in KeyVault) has some support for multiple clouds but we haven't really tested this well.

2 and 3 are easy to get working in a smoother way - we just haven't done it because a) no one has asked us for it and b) we have limited ability to test it.
I'd be very really happy to work with you to get this going.

@ianhelle ianhelle added the question Further information is requested label Jun 16, 2021
@ianhelle ianhelle linked a pull request Sep 2, 2021 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants