search

microsoft / coe-starter-kit

Other
736 stars 215 forks source link

[CoE Starter Kit - BUG] CrmDefaultActivity Teams & Developer environment last activity related to CrmDefaultActivity. Read operations changing modified date #5968

Open millsmi opened 1 year ago

millsmi commented 1 year ago

Does this bug already exist in our backlog?

Describe the issue

We have an issue whereby every Saturday evening, the last activity timestamp on Developer and Teams environments gets updated. This activity stops unused environments from getting deactivated and then deleted.

Microsoft support have so far been exceedingly unhelpful on the matter which has been opened for >3 months and has been re-assigned several times. The last update I received from them brought this to my attention as the cause of the issue.

AAD Object is this azure-logic-apps/1.0 (workflow ce92dadc9ada4a8889d6257ff687881d; version 08585143735020968147) microsoft-flow/1.0 CommonDataService,

Through our investigation, we see in our unified audit logs CrmDefaultActivity events linked to our CoE environment and corresponds to when the environment last activity gets updated, the same Azure logic app workflow id and our Power Platform CoE admin service account.

The problem is, we do not use Azure logic apps and this id is not a Power Automate flow id but the authenticating id is our Power Platform CoE service account.

Everything seems to be pointing to the CoE toolkit as the root cause of our issues and I am wondering if this is something you are aware of and can identify the root cause.

Expected Behavior

.

What solution are you experiencing the issue with?

Core

What solution version are you using?

4.8

What app or flow are you having the issue with?

Unknown

What method are you using to get inventory and telemetry?

Cloud flows

Steps To Reproduce

Create brand new Team or developer environment Wait until Monday morning Check the environment last activity Last activity always has a timestamp from Saturday evening

Anything else?

No response

AB#2207

Jenefer-Monroe commented 1 year ago

Unfortunately this is a product bug. We do read activities only, and that is not supposed to update the modified date on an environment. The product team fixed this in the past (many months ago) so it may be a regression.

My suggestion would be to give this pointer to the support person you are working with, and we will also press internally.

millsmi commented 1 year ago

Jenefer, thank you for your insight. I have indeed provided this to the MS support engineer.

millsmi commented 1 year ago

Hi Jenefer,

If you could press internally also I would appreciate it. I have no confidence in Microsoft support being able resolve this and seem to be just going around in circles these last few months.

Jenefer-Monroe commented 1 year ago

Yes we certainly will, thanks for being patient!

millsmi commented 1 year ago

Hi Jenefer, the issue seems to be fixed for the MS Teams environments. Time stamp is July 8th. We are still seeing the same issue with Developer licenses and MS support still seem to be struggling. Any help on this would be appreciated.

On another note, for the Data Export feature for the CoE Toolkit, our Azure team need to know a little more about the first time authorization backend process for the cross platform integration (PPAC to Gen2 DL). Again MS support is struggling with the answer.

This is the question being asked by our Cloud Architect who is blocking the integration for us at the moment. "The SPN will get created during the AAD authorization process - I need to understand this a bit more. This is sounding more like a managed identity. Usually SPN is created as a separate entity. MI is just like SPN but its life cycle is the same as the application. SPN has a "permanent" life cycle."

Not sure you have the answer to this one, but I bet you know someone who does :-)