Closed kodjo-anipah closed 1 month ago
@waab76 Requesting a status update on this issue.
@BBruce-Graylog @kodjo-anipah apologies for the delay on this one. However, it would seem that Microsoft has forced our hand a bit on the Teams Notification front. They are retiring O365 Connectors on October 1st in favor of Workflows, so starting then the current implementation of the Graylog Microsoft Teams Notification will be completely broken, regardless of your URL being valid. But we already have a new notification type PR up to be released by the September maintenance release into 5.2.x and 6.0.x. This will resolve both the invalid URL checks and Microsoft's retiring of connectors.
In the meantime, if this environment is on Graylog 6.0.x the new Custom HTTP Notification can be configured to feed Teams Notifications. If you would like some help getting that going, I'd be happy to help out.
Current Behavior
When attempting to configure a webhook with a .office365.us host endpoint within TeamsEventNotificationConfig, a validation error is thrown. This limitation prevents the configuration of notifications for Microsoft GCC environments.
Possible Solution
Remove or improve host matching with keyword
office
i s encountered.Steps to Reproduce (for bugs)
Create a new TeamsEventNotification and try to configure a webhook url ending with .office365.us.
Context
Your Environment