Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrect SharePoint Online location #356

Open
germain-italic opened this issue Jun 28, 2023 · 3 comments
Open

Incorrect SharePoint Online location #356

germain-italic opened this issue Jun 28, 2023 · 3 comments

Comments

@germain-italic
Copy link

Hello, we are having trouble with geolocation on our SharePoint Online classic intranet (requires login throught the portal login.microsoftonline.com).

All our visitors connect from the same VPN from multiple offices, in the same country (France).

But tracked visits are spawned accross all over the world and all continents (EU 60%, 30% North America, Asia, India...).

We cannot use TrackingSpamPrevention as I understand that it would block all traffic tied to Microsoft/Azure, so there would be no more tracking.

We have tried to block IPs from the official MS list but we have seen no change.

We are thinking of banning referrers from login.microsoftonline.com but I'm afraid this would cut all legitimate users.

Have your ever encountered this issue, is there any workaround?

@sgiehl
Copy link
Member

sgiehl commented Jun 30, 2023

Hey @germain-italic
I'm not fully sure what your real problem is. Are there requests being tracked from users that shouldn't be tracked? Or are unsers connected through vpn tracked with an incorrect location?
The latter one could be caused by not using the correct IP for geolocation. If all users are coming though a vpn proxy, you might need to configure that in Matomo

@germain-italic
Copy link
Author

Hello @sgiehl,

unsers connected through vpn tracked with an incorrect location?

This one. I'll check if I find some information about the VPN!

@germain-italic
Copy link
Author

I finally got some information: there is no proxy, the VPN allocates the expected public IP address which is geolocated accurately. So we are still having ghosts located in USA on this intranet which is only open to people using the VPN, and who were not showing up when we used Google Analytics. I'm stuck.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants