Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

Any solution for internal IP address capturing in Microsoft Dynamics 365 audit trail??

(0) ShareShare
ReportReport
Posted on by
Are there solutions or compensatory controls for capturing internal client IP address in Dynamics 365 CRM audit trail for clients who use cloud based Dynamics 365 CRM (Azure) from their organizational network. By design, audit trail of MS Dynamics CRM captures ongoing IP address (i.e. public IP) of the clients network in the CRM audit trail for all users accessing the application, which can be meaningless when investigating cases of users repudiating activities performed using their account either deliberately (for cover up of unauthorized activities) or genuine case of compromise. As such, to prove the cases beyond reasonable doubt and hold the abuser responsible/accountable, the location or machine/workstation from where such activities was carried out on the CRM is critical and only internal IP information on the audit trail can provide lead on how or who carried out the activity. In what way can a client customize the CRM audit trail either by integrating with a third party tool or implementing other compensatory control to ensure non-repudiation of users' activities on the CRM? Can 2FA (token/OTP: what you have) be integrated with Dynamics 365 CRM at login or IP translation happen in some way via integration with other solutions, etc. Need direction on how to achieve this please. http://oxleyconsults.com.ng

*This post is locked for comments

  • RE: Any solution for internal IP address capturing in Microsoft Dynamics 365 audit trail??

    Thanks David.

    I appreciate your response.

  • David Jennaway Profile Picture
    David Jennaway 14,063 on at
    RE: Any solution for internal IP address capturing in Microsoft Dynamics 365 audit trail??

    Anything happening within CRM auditing necessarily only uses the information that the CRM Server receives, which will be the public IP address. In theory it might be possible to add the internal IP as an attribute on all entities, and have client-side script on the form populate this on every create/update request via the form, and this would add the data to the CRM audit trail. However, this only works for changes via CRM forms, so wouldn't cover other means of making changes (e.g. via workflow or editable grids), so I don't think this would be practical.

    Authentication to Dynamics 365 CRM is via Office 365 authentication, and can be configured to use 2FA, so that is probably your best option

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Daivat Vartak – Community Spotlight

We are honored to recognize Daivat Vartak as our March 2025 Community…

Announcing Our 2025 Season 1 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Kudos to the February Top 10 Community Stars!

Thanks for all your good work in the Community!

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 292,516 Super User 2025 Season 1

#2
Martin Dráb Profile Picture

Martin Dráb 231,409 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans