Data fetch failed (Invalid Config.) with Solutions/LastPass

[ChristopheDMTL]

Hello,

I think there is a problem with the solution, after deploying the solution from the content hub, I was able to go into the connector and configure the connection to LastPass, but the table never created.

And I have these two alerts that keep repeating:

Thanks

[github-actions[bot]]

Thank you for submitting an Issue to the Azure Sentinel GitHub repo! You should expect an initial response to your Issue from the team within 5 business days. Note that this response may be delayed during holiday periods. For urgent, production-affecting issues please raise a support ticket via the Azure Portal.

[github-actions[bot]]

Thank you for submitting an Issue to the Azure Sentinel GitHub repo! You should expect an initial response to your Issue from the team within 5 business days. Note that this response may be delayed during holiday periods. For urgent, production-affecting issues please raise a support ticket via the Azure Portal.

[github-actions[bot]]

Thank you for submitting an Issue to the Azure Sentinel GitHub repo! You should expect an initial response to your Issue from the team within 5 business days. Note that this response may be delayed during holiday periods. For urgent, production-affecting issues please raise a support ticket via the Azure Portal.

[ashishsyal]

Hi - Are you still facing the issue?

[ashishsyal]

@ChristopheDMTL - Please check and let us know if the issue is still persisting for you.

[ChristopheDMTL]

Hello,

Thank you for your feedback, but I couldn't wait for the resolution. We finally built our own solution.

Thanks

From: ashishsyal @.> Sent: January 5, 2023 7:58 AM To: Azure/Azure-Sentinel @.> Cc: ChristopheDMTL @.>; Mention @.> Subject: Re: [Azure/Azure-Sentinel] Data fetch failed (Invalid Config.) with Solutions/LastPass (Issue #6202)

@ChristopheDMTLhttps://github.com/ChristopheDMTL - Please check and let us know if the issue is still persisting for you.

— Reply to this email directly, view it on GitHubhttps://github.com/Azure/Azure-Sentinel/issues/6202#issuecomment-1372183525, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AXP5D4ZLTFUQGSAWHEAQQ4TWQ3AMPANCNFSM6AAAAAAQSNVFE4. You are receiving this because you were mentioned.Message ID: @.@.>>

[github-actions[bot]]

Thank you for submitting an Issue to the Azure Sentinel GitHub repo! You should expect an initial response to your Issue from the team within 5 business days. Note that this response may be delayed during holiday periods. For urgent, production-affecting issues please raise a support ticket via the Azure Portal.

[github-actions[bot]]

Thank you for submitting an Issue to the Azure Sentinel GitHub repo! You should expect an initial response to your Issue from the team within 5 business days. Note that this response may be delayed during holiday periods. For urgent, production-affecting issues please raise a support ticket via the Azure Portal.

[github-actions[bot]]

Thank you for submitting an Issue to the Azure Sentinel GitHub repo! You should expect an initial response to your Issue from the team within 5 business days. Note that this response may be delayed during holiday periods. For urgent, production-affecting issues please raise a support ticket via the Azure Portal.

[v-rbajaj]

@ChristopheDMTL, Thanks for the confirmation, we are closing this issue.

[github-actions[bot]]

Thank you for submitting an Issue to the Azure Sentinel GitHub repo! You should expect an initial response to your Issue from the team within 5 business days. Note that this response may be delayed during holiday periods. For urgent, production-affecting issues please raise a support ticket via the Azure Portal.