Microsoft has thrown some enterprises right into a spin after confirming that, with only some months’ discover, Workplace 365 connectors inside Groups might be reduce.
The connectors and webhooks are used to plumb workflows right into a Groups channel. For instance, customers would possibly use them to submit an replace right into a chat stream. This implies you possibly can learn content material and repair updates instantly in a Groups channel that originated from one thing like a ticketing platform or a notification from a CI/CD system.
That is the kind of glue that enterprises rely upon to make totally different programs talk. Or not less than it was. From August 15, 2024, Microsoft will block all Connector creation inside all clouds. From October 1, 2024, all connectors inside all clouds will cease working.
Microsoft has been a little bit obscure on precisely why it’s doing this. Its suggestion is for customers to change to Energy Automate workflows to “be sure that your integrations are constructed on an structure that may develop with your corporation wants and supply most safety of your info.”
It added, “Customers at present using Workplace 365 connectors ought to transition to Energy Automate to take care of easy operation of their providers.”
Customers have been lower than impressed by the information. Feedback to the corporate’s submit have handed the 100 mark and are typically adverse, with some describing the plans as “a grasping money seize” and others reacting with bewilderment at Microsoft’s choice:
“Do Microsoft not be taught from inadequate transition deadlines? You’ve given customers 3 months, 2 of that are throughout peak vacation season the place many employees might be on annual depart for elements of it, to maneuver service integrations away from connector format to presumably one thing they’ve by no means even checked out. Why?”
Register readers have additionally been in contact to share the impression the change is having on them. One, who makes use of RSS feeds and webhooks to ship CI/CD notifications to channels, agreed with feedback that the change was a “PITA with no profit to the shopper” and famous that the valuable few months of discover given wasn’t very lengthy.
One other stated, “It is already hitting us since they’ve determined of their infinite knowledge to incorporate a SPAM on every submit made to a webhook telling us that the webhook goes to cease working. The pressing notice of this SPAM makes it appear extra essential than the message it’s appended to.”
Connector spam (credit score: A Register Reader) – click on to enlarge
Our reader went on to say, “We’re utilizing webhooks in a number of Groups channels in order that e.g. our monitoring system can submit an alert to the correct crew to go repair an issue. Or from our ticketing system to submit ‘Hey, there is a new ticket in your queue: $topic.’
“I rely not less than 60 posts through webhooks since this alteration began to have an effect on us and each has the identical spam appended to the tip of it.”
The Register invited Microsoft to touch upon the explanations behind its choice, the discover interval, and the problems reported by customers with Energy Automate workflows. Ought to the corporate reply, we’ll replace this piece.
Within the meantime, we’ll depart the final phrase to a Register reader coping with the fallout from the upcoming retirement.
“MS are proving how nicely they perceive the enterprise once more…” ®
Microsoft has thrown some enterprises right into a spin after confirming that, with only some months’ discover, Workplace 365 connectors inside Groups might be reduce.
The connectors and webhooks are used to plumb workflows right into a Groups channel. For instance, customers would possibly use them to submit an replace right into a chat stream. This implies you possibly can learn content material and repair updates instantly in a Groups channel that originated from one thing like a ticketing platform or a notification from a CI/CD system.
That is the kind of glue that enterprises rely upon to make totally different programs talk. Or not less than it was. From August 15, 2024, Microsoft will block all Connector creation inside all clouds. From October 1, 2024, all connectors inside all clouds will cease working.
Microsoft has been a little bit obscure on precisely why it’s doing this. Its suggestion is for customers to change to Energy Automate workflows to “be sure that your integrations are constructed on an structure that may develop with your corporation wants and supply most safety of your info.”
It added, “Customers at present using Workplace 365 connectors ought to transition to Energy Automate to take care of easy operation of their providers.”
Customers have been lower than impressed by the information. Feedback to the corporate’s submit have handed the 100 mark and are typically adverse, with some describing the plans as “a grasping money seize” and others reacting with bewilderment at Microsoft’s choice:
“Do Microsoft not be taught from inadequate transition deadlines? You’ve given customers 3 months, 2 of that are throughout peak vacation season the place many employees might be on annual depart for elements of it, to maneuver service integrations away from connector format to presumably one thing they’ve by no means even checked out. Why?”
Register readers have additionally been in contact to share the impression the change is having on them. One, who makes use of RSS feeds and webhooks to ship CI/CD notifications to channels, agreed with feedback that the change was a “PITA with no profit to the shopper” and famous that the valuable few months of discover given wasn’t very lengthy.
One other stated, “It is already hitting us since they’ve determined of their infinite knowledge to incorporate a SPAM on every submit made to a webhook telling us that the webhook goes to cease working. The pressing notice of this SPAM makes it appear extra essential than the message it’s appended to.”
Connector spam (credit score: A Register Reader) – click on to enlarge
Our reader went on to say, “We’re utilizing webhooks in a number of Groups channels in order that e.g. our monitoring system can submit an alert to the correct crew to go repair an issue. Or from our ticketing system to submit ‘Hey, there is a new ticket in your queue: $topic.’
“I rely not less than 60 posts through webhooks since this alteration began to have an effect on us and each has the identical spam appended to the tip of it.”
The Register invited Microsoft to touch upon the explanations behind its choice, the discover interval, and the problems reported by customers with Energy Automate workflows. Ought to the corporate reply, we’ll replace this piece.
Within the meantime, we’ll depart the final phrase to a Register reader coping with the fallout from the upcoming retirement.
“MS are proving how nicely they perceive the enterprise once more…” ®
Microsoft has thrown some enterprises right into a spin after confirming that, with only some months’ discover, Workplace 365 connectors inside Groups might be reduce.
The connectors and webhooks are used to plumb workflows right into a Groups channel. For instance, customers would possibly use them to submit an replace right into a chat stream. This implies you possibly can learn content material and repair updates instantly in a Groups channel that originated from one thing like a ticketing platform or a notification from a CI/CD system.
That is the kind of glue that enterprises rely upon to make totally different programs talk. Or not less than it was. From August 15, 2024, Microsoft will block all Connector creation inside all clouds. From October 1, 2024, all connectors inside all clouds will cease working.
Microsoft has been a little bit obscure on precisely why it’s doing this. Its suggestion is for customers to change to Energy Automate workflows to “be sure that your integrations are constructed on an structure that may develop with your corporation wants and supply most safety of your info.”
It added, “Customers at present using Workplace 365 connectors ought to transition to Energy Automate to take care of easy operation of their providers.”
Customers have been lower than impressed by the information. Feedback to the corporate’s submit have handed the 100 mark and are typically adverse, with some describing the plans as “a grasping money seize” and others reacting with bewilderment at Microsoft’s choice:
“Do Microsoft not be taught from inadequate transition deadlines? You’ve given customers 3 months, 2 of that are throughout peak vacation season the place many employees might be on annual depart for elements of it, to maneuver service integrations away from connector format to presumably one thing they’ve by no means even checked out. Why?”
Register readers have additionally been in contact to share the impression the change is having on them. One, who makes use of RSS feeds and webhooks to ship CI/CD notifications to channels, agreed with feedback that the change was a “PITA with no profit to the shopper” and famous that the valuable few months of discover given wasn’t very lengthy.
One other stated, “It is already hitting us since they’ve determined of their infinite knowledge to incorporate a SPAM on every submit made to a webhook telling us that the webhook goes to cease working. The pressing notice of this SPAM makes it appear extra essential than the message it’s appended to.”
Connector spam (credit score: A Register Reader) – click on to enlarge
Our reader went on to say, “We’re utilizing webhooks in a number of Groups channels in order that e.g. our monitoring system can submit an alert to the correct crew to go repair an issue. Or from our ticketing system to submit ‘Hey, there is a new ticket in your queue: $topic.’
“I rely not less than 60 posts through webhooks since this alteration began to have an effect on us and each has the identical spam appended to the tip of it.”
The Register invited Microsoft to touch upon the explanations behind its choice, the discover interval, and the problems reported by customers with Energy Automate workflows. Ought to the corporate reply, we’ll replace this piece.
Within the meantime, we’ll depart the final phrase to a Register reader coping with the fallout from the upcoming retirement.
“MS are proving how nicely they perceive the enterprise once more…” ®
Microsoft has thrown some enterprises right into a spin after confirming that, with only some months’ discover, Workplace 365 connectors inside Groups might be reduce.
The connectors and webhooks are used to plumb workflows right into a Groups channel. For instance, customers would possibly use them to submit an replace right into a chat stream. This implies you possibly can learn content material and repair updates instantly in a Groups channel that originated from one thing like a ticketing platform or a notification from a CI/CD system.
That is the kind of glue that enterprises rely upon to make totally different programs talk. Or not less than it was. From August 15, 2024, Microsoft will block all Connector creation inside all clouds. From October 1, 2024, all connectors inside all clouds will cease working.
Microsoft has been a little bit obscure on precisely why it’s doing this. Its suggestion is for customers to change to Energy Automate workflows to “be sure that your integrations are constructed on an structure that may develop with your corporation wants and supply most safety of your info.”
It added, “Customers at present using Workplace 365 connectors ought to transition to Energy Automate to take care of easy operation of their providers.”
Customers have been lower than impressed by the information. Feedback to the corporate’s submit have handed the 100 mark and are typically adverse, with some describing the plans as “a grasping money seize” and others reacting with bewilderment at Microsoft’s choice:
“Do Microsoft not be taught from inadequate transition deadlines? You’ve given customers 3 months, 2 of that are throughout peak vacation season the place many employees might be on annual depart for elements of it, to maneuver service integrations away from connector format to presumably one thing they’ve by no means even checked out. Why?”
Register readers have additionally been in contact to share the impression the change is having on them. One, who makes use of RSS feeds and webhooks to ship CI/CD notifications to channels, agreed with feedback that the change was a “PITA with no profit to the shopper” and famous that the valuable few months of discover given wasn’t very lengthy.
One other stated, “It is already hitting us since they’ve determined of their infinite knowledge to incorporate a SPAM on every submit made to a webhook telling us that the webhook goes to cease working. The pressing notice of this SPAM makes it appear extra essential than the message it’s appended to.”
Connector spam (credit score: A Register Reader) – click on to enlarge
Our reader went on to say, “We’re utilizing webhooks in a number of Groups channels in order that e.g. our monitoring system can submit an alert to the correct crew to go repair an issue. Or from our ticketing system to submit ‘Hey, there is a new ticket in your queue: $topic.’
“I rely not less than 60 posts through webhooks since this alteration began to have an effect on us and each has the identical spam appended to the tip of it.”
The Register invited Microsoft to touch upon the explanations behind its choice, the discover interval, and the problems reported by customers with Energy Automate workflows. Ought to the corporate reply, we’ll replace this piece.
Within the meantime, we’ll depart the final phrase to a Register reader coping with the fallout from the upcoming retirement.
“MS are proving how nicely they perceive the enterprise once more…” ®
Microsoft has thrown some enterprises right into a spin after confirming that, with only some months’ discover, Workplace 365 connectors inside Groups might be reduce.
The connectors and webhooks are used to plumb workflows right into a Groups channel. For instance, customers would possibly use them to submit an replace right into a chat stream. This implies you possibly can learn content material and repair updates instantly in a Groups channel that originated from one thing like a ticketing platform or a notification from a CI/CD system.
That is the kind of glue that enterprises rely upon to make totally different programs talk. Or not less than it was. From August 15, 2024, Microsoft will block all Connector creation inside all clouds. From October 1, 2024, all connectors inside all clouds will cease working.
Microsoft has been a little bit obscure on precisely why it’s doing this. Its suggestion is for customers to change to Energy Automate workflows to “be sure that your integrations are constructed on an structure that may develop with your corporation wants and supply most safety of your info.”
It added, “Customers at present using Workplace 365 connectors ought to transition to Energy Automate to take care of easy operation of their providers.”
Customers have been lower than impressed by the information. Feedback to the corporate’s submit have handed the 100 mark and are typically adverse, with some describing the plans as “a grasping money seize” and others reacting with bewilderment at Microsoft’s choice:
“Do Microsoft not be taught from inadequate transition deadlines? You’ve given customers 3 months, 2 of that are throughout peak vacation season the place many employees might be on annual depart for elements of it, to maneuver service integrations away from connector format to presumably one thing they’ve by no means even checked out. Why?”
Register readers have additionally been in contact to share the impression the change is having on them. One, who makes use of RSS feeds and webhooks to ship CI/CD notifications to channels, agreed with feedback that the change was a “PITA with no profit to the shopper” and famous that the valuable few months of discover given wasn’t very lengthy.
One other stated, “It is already hitting us since they’ve determined of their infinite knowledge to incorporate a SPAM on every submit made to a webhook telling us that the webhook goes to cease working. The pressing notice of this SPAM makes it appear extra essential than the message it’s appended to.”
Connector spam (credit score: A Register Reader) – click on to enlarge
Our reader went on to say, “We’re utilizing webhooks in a number of Groups channels in order that e.g. our monitoring system can submit an alert to the correct crew to go repair an issue. Or from our ticketing system to submit ‘Hey, there is a new ticket in your queue: $topic.’
“I rely not less than 60 posts through webhooks since this alteration began to have an effect on us and each has the identical spam appended to the tip of it.”
The Register invited Microsoft to touch upon the explanations behind its choice, the discover interval, and the problems reported by customers with Energy Automate workflows. Ought to the corporate reply, we’ll replace this piece.
Within the meantime, we’ll depart the final phrase to a Register reader coping with the fallout from the upcoming retirement.
“MS are proving how nicely they perceive the enterprise once more…” ®
Microsoft has thrown some enterprises right into a spin after confirming that, with only some months’ discover, Workplace 365 connectors inside Groups might be reduce.
The connectors and webhooks are used to plumb workflows right into a Groups channel. For instance, customers would possibly use them to submit an replace right into a chat stream. This implies you possibly can learn content material and repair updates instantly in a Groups channel that originated from one thing like a ticketing platform or a notification from a CI/CD system.
That is the kind of glue that enterprises rely upon to make totally different programs talk. Or not less than it was. From August 15, 2024, Microsoft will block all Connector creation inside all clouds. From October 1, 2024, all connectors inside all clouds will cease working.
Microsoft has been a little bit obscure on precisely why it’s doing this. Its suggestion is for customers to change to Energy Automate workflows to “be sure that your integrations are constructed on an structure that may develop with your corporation wants and supply most safety of your info.”
It added, “Customers at present using Workplace 365 connectors ought to transition to Energy Automate to take care of easy operation of their providers.”
Customers have been lower than impressed by the information. Feedback to the corporate’s submit have handed the 100 mark and are typically adverse, with some describing the plans as “a grasping money seize” and others reacting with bewilderment at Microsoft’s choice:
“Do Microsoft not be taught from inadequate transition deadlines? You’ve given customers 3 months, 2 of that are throughout peak vacation season the place many employees might be on annual depart for elements of it, to maneuver service integrations away from connector format to presumably one thing they’ve by no means even checked out. Why?”
Register readers have additionally been in contact to share the impression the change is having on them. One, who makes use of RSS feeds and webhooks to ship CI/CD notifications to channels, agreed with feedback that the change was a “PITA with no profit to the shopper” and famous that the valuable few months of discover given wasn’t very lengthy.
One other stated, “It is already hitting us since they’ve determined of their infinite knowledge to incorporate a SPAM on every submit made to a webhook telling us that the webhook goes to cease working. The pressing notice of this SPAM makes it appear extra essential than the message it’s appended to.”
Connector spam (credit score: A Register Reader) – click on to enlarge
Our reader went on to say, “We’re utilizing webhooks in a number of Groups channels in order that e.g. our monitoring system can submit an alert to the correct crew to go repair an issue. Or from our ticketing system to submit ‘Hey, there is a new ticket in your queue: $topic.’
“I rely not less than 60 posts through webhooks since this alteration began to have an effect on us and each has the identical spam appended to the tip of it.”
The Register invited Microsoft to touch upon the explanations behind its choice, the discover interval, and the problems reported by customers with Energy Automate workflows. Ought to the corporate reply, we’ll replace this piece.
Within the meantime, we’ll depart the final phrase to a Register reader coping with the fallout from the upcoming retirement.
“MS are proving how nicely they perceive the enterprise once more…” ®
Microsoft has thrown some enterprises right into a spin after confirming that, with only some months’ discover, Workplace 365 connectors inside Groups might be reduce.
The connectors and webhooks are used to plumb workflows right into a Groups channel. For instance, customers would possibly use them to submit an replace right into a chat stream. This implies you possibly can learn content material and repair updates instantly in a Groups channel that originated from one thing like a ticketing platform or a notification from a CI/CD system.
That is the kind of glue that enterprises rely upon to make totally different programs talk. Or not less than it was. From August 15, 2024, Microsoft will block all Connector creation inside all clouds. From October 1, 2024, all connectors inside all clouds will cease working.
Microsoft has been a little bit obscure on precisely why it’s doing this. Its suggestion is for customers to change to Energy Automate workflows to “be sure that your integrations are constructed on an structure that may develop with your corporation wants and supply most safety of your info.”
It added, “Customers at present using Workplace 365 connectors ought to transition to Energy Automate to take care of easy operation of their providers.”
Customers have been lower than impressed by the information. Feedback to the corporate’s submit have handed the 100 mark and are typically adverse, with some describing the plans as “a grasping money seize” and others reacting with bewilderment at Microsoft’s choice:
“Do Microsoft not be taught from inadequate transition deadlines? You’ve given customers 3 months, 2 of that are throughout peak vacation season the place many employees might be on annual depart for elements of it, to maneuver service integrations away from connector format to presumably one thing they’ve by no means even checked out. Why?”
Register readers have additionally been in contact to share the impression the change is having on them. One, who makes use of RSS feeds and webhooks to ship CI/CD notifications to channels, agreed with feedback that the change was a “PITA with no profit to the shopper” and famous that the valuable few months of discover given wasn’t very lengthy.
One other stated, “It is already hitting us since they’ve determined of their infinite knowledge to incorporate a SPAM on every submit made to a webhook telling us that the webhook goes to cease working. The pressing notice of this SPAM makes it appear extra essential than the message it’s appended to.”
Connector spam (credit score: A Register Reader) – click on to enlarge
Our reader went on to say, “We’re utilizing webhooks in a number of Groups channels in order that e.g. our monitoring system can submit an alert to the correct crew to go repair an issue. Or from our ticketing system to submit ‘Hey, there is a new ticket in your queue: $topic.’
“I rely not less than 60 posts through webhooks since this alteration began to have an effect on us and each has the identical spam appended to the tip of it.”
The Register invited Microsoft to touch upon the explanations behind its choice, the discover interval, and the problems reported by customers with Energy Automate workflows. Ought to the corporate reply, we’ll replace this piece.
Within the meantime, we’ll depart the final phrase to a Register reader coping with the fallout from the upcoming retirement.
“MS are proving how nicely they perceive the enterprise once more…” ®
Microsoft has thrown some enterprises right into a spin after confirming that, with only some months’ discover, Workplace 365 connectors inside Groups might be reduce.
The connectors and webhooks are used to plumb workflows right into a Groups channel. For instance, customers would possibly use them to submit an replace right into a chat stream. This implies you possibly can learn content material and repair updates instantly in a Groups channel that originated from one thing like a ticketing platform or a notification from a CI/CD system.
That is the kind of glue that enterprises rely upon to make totally different programs talk. Or not less than it was. From August 15, 2024, Microsoft will block all Connector creation inside all clouds. From October 1, 2024, all connectors inside all clouds will cease working.
Microsoft has been a little bit obscure on precisely why it’s doing this. Its suggestion is for customers to change to Energy Automate workflows to “be sure that your integrations are constructed on an structure that may develop with your corporation wants and supply most safety of your info.”
It added, “Customers at present using Workplace 365 connectors ought to transition to Energy Automate to take care of easy operation of their providers.”
Customers have been lower than impressed by the information. Feedback to the corporate’s submit have handed the 100 mark and are typically adverse, with some describing the plans as “a grasping money seize” and others reacting with bewilderment at Microsoft’s choice:
“Do Microsoft not be taught from inadequate transition deadlines? You’ve given customers 3 months, 2 of that are throughout peak vacation season the place many employees might be on annual depart for elements of it, to maneuver service integrations away from connector format to presumably one thing they’ve by no means even checked out. Why?”
Register readers have additionally been in contact to share the impression the change is having on them. One, who makes use of RSS feeds and webhooks to ship CI/CD notifications to channels, agreed with feedback that the change was a “PITA with no profit to the shopper” and famous that the valuable few months of discover given wasn’t very lengthy.
One other stated, “It is already hitting us since they’ve determined of their infinite knowledge to incorporate a SPAM on every submit made to a webhook telling us that the webhook goes to cease working. The pressing notice of this SPAM makes it appear extra essential than the message it’s appended to.”
Connector spam (credit score: A Register Reader) – click on to enlarge
Our reader went on to say, “We’re utilizing webhooks in a number of Groups channels in order that e.g. our monitoring system can submit an alert to the correct crew to go repair an issue. Or from our ticketing system to submit ‘Hey, there is a new ticket in your queue: $topic.’
“I rely not less than 60 posts through webhooks since this alteration began to have an effect on us and each has the identical spam appended to the tip of it.”
The Register invited Microsoft to touch upon the explanations behind its choice, the discover interval, and the problems reported by customers with Energy Automate workflows. Ought to the corporate reply, we’ll replace this piece.
Within the meantime, we’ll depart the final phrase to a Register reader coping with the fallout from the upcoming retirement.
“MS are proving how nicely they perceive the enterprise once more…” ®