David Blain

> Well. one comment here @dabla - I think you should not publish it under `apache-airflow-providers-*` name. While we do not have a way to prevent it - this might...

> We have multiple DAG's interacting with MS Graph API endpoints, and as we want to avoid custom code as much as possible as we have to handle lot's of...

> I think we can close this PR in favor of [apache/airflow#38111](https://github.com/apache/airflow/pull/38111) ? Hey Elad yes this one can be closed.

> WDYT Seems like the deco method is considered as calling he execute method of the PythonOperator outside of the TaskInstance, this is the protection mechanism which would warn you...

> Thanks for the investigation and feedback, @Taragolis and @dabla! > > Yes, everything still works despite the warning message. I created this issue just as a "preventive" measure because...

Hello, I tested following PR and they are all working a expected: - [38111](https://github.com/apache/airflow/pull/38111) - [39237](https://github.com/apache/airflow/pull/39237) - [39304](https://github.com/apache/airflow/pull/39304) - [39207](https://github.com/apache/airflow/pull/39207) So for me everything related to MSGraphOperator is good.

I know there is still an issue with the MSGraphSensor in that sense that it’s not working correctly in an async way and sometimes an event loop closed error can...

Following 3 PR suffer from the same issues with the MSGraphSenor which has been fixed in [#39304](https://github.com/apache/airflow/pull/39304): [#38111](https://github.com/apache/airflow/pull/38111) [#39237]( https://github.com/apache/airflow/pull/39237) [#39207]( https://github.com/apache/airflow/pull/39207)

> > I know there is still an issue with the MSGraphSensor in that sense that it’s not working correctly in an async way and sometimes an event loop closed...

> > I know Elad I just wanted to make you guys aware of it. > > If there is regression we can make RC2 then it will be included....