Disabled Connectors

Question

We have noticed that in some tenants, connectors that were configured are showing up as disabled. One of my colleagues thinks that&nbsp;if there is no activity during an unspecified period of time, it goes grey and seems "disabled". Once some activity is detected, it again goes green and shows alive. This is something new MS hasn't disclosed and should be tested, but has been seen in other clients workspaces. Has anyone else seen this type of behavior? Can anyone from MSFT confirm that this is by design?

rod_trent · Answer

Hi, Dean. Its moreso that the rule failed to run.I believe this better describes it:  https://cda.ms/32G

dean_gross · Answer

Rod_Trent&nbsp;Thanks, I had not seen that article. When I review the analytic rules, I am not seeing any that show Auto Disabled. Any other ideas about what might be going on? When I look at an associated workbook and run a log query, It shows a few events from Oct 15, but now the connector is disabled. I need to get a better understanding about what is happening

rod_trent · Answer

Which connector is it, btw? MCAS?

dean_gross · Answer

No, it is Azure Activity. this is occurring in multiple CSP tenants that should not have any significant Azure activity because they are primarily used for O365. I wanted to use Azure Activity connector to help make sure that nothing malicious does occur with azure resources.

garybushey · Answer

I have seen this if there data has not flowed in for a while, the table is considered empty (if you look at the data ingestion summary when clicking on the data connector it will show that no data has come in at all) so the data connector is assumed to be disconnected.

Forum Discussion

Disabled Connectors

7 Replies

Resources