-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
1Password connector deployment #11428
Comments
Hi @abrownsyn, Thanks for flagging this issue, we will investigate this issue and get back to you with some updates. Thanks! |
@abrownsyn, Could you please share the error details with screenshots, and can you check with below steps in solution which have the 1Password connector - Thanks! |
@v-sudkharat When follow your steps I get back to deploy to azure screen. I'm attaching some screens below, if it's easier we can screen a video conference next week. |
@abrownsyn, Sure. will do. Please check in your environment, Is the Workspace Name which you have entered are in a same Resource Group. So, Please validate Workspace Name, Resource Group and Region are correctly added as input filed. Thanks! |
@abrownsyn, Waiting for your response on above comment. Thanks! |
@v-sudkharat sorry for the delay but that fixed it thank you for your help |
@abrownsyn, Welcome. |
Describe the bug
When following the directions on to set up data connector, I click on deploy azure enter the required information.The deployment then fails (Code: ParentResourceNotFound) I will also attach a screenshot below.
I also found the steps on Medium "https://rogierdijkman.medium.com/1password-microsoft-sentinel-solution-7e77d98957cd"
the link in the that page is not working.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
After the setup is completed, a summary will be displayed showing the results of the deployed templates.
After some time, Microsoft Sentinel will start receiving data from the 1Password API, and the data connector will show as connected.
Screenshots
The text was updated successfully, but these errors were encountered: