We are monitoring batch jobs using Application Insights telemetry.
We have identified that BatchTaskStart events are correctly logged
under the executing legal entity however BatchTaskFinished events
for the same task are being logged under a different legal entity.
the same ActivityId has BatchTaskStart under one legal entity and
BatchTaskFinished under a different legal entity.
- BatchTaskStart → logged under executing legal entity ✓
- BatchTaskFinished → logged under different legal entity ✓
- Same ActivityId confirmed to have start and finish under different legal entities
- Both AOS servers handle jobs for both legal entities so this is not
a server configuration issue
- Application Insights connection string is configured at environment
level not per legal entity
Is this expected behaviour in D365 F&O batch telemetry? If so what
is the reason the BatchTaskFinished event is logged under a different
legal entity than the one the job executed under? Is there a
configuration or fix to align the finish event legal entity with
the start event legal entity?

Report
All responses (
Answers (