Forum Discussion
The dreaded App@SharePoint user name problem
I've created a (regular) ticket in Office 365, and this is the response I got:
The Account app@sharepoint is related to the SharePoint Applications (Auditing logs/Virus), it is a system account, belongs to the SharePoint Farms infrastructure, it was created to run on all Site Collections/Personal sites to collect auditing information. When the user provides some changes for his own Site Collection, or enables features or activates the site Auditing logs, his own account does not have the write permissions on the SharePoint Farm and this account it will be used to run and collect all the necessary information to be provided to the customer. Microsoft has set up a few security accounts to run in all Farms, in order for our customer to do some tasks, and get the required information. Also it is necessary for user security, for these accounts to always track the Site Collection searching for viruses that can be uploaded into SharePoint. Microsoft will not change that, all Farms have the same configuration and this same system account, and all Site Collections will use this account if they need to do it.
What Activities Should the customer expect from this account?
From the Customer side nothing will be expected, everything will be running normal, as should be, this account will not affect the Site Collection functionality or personal site, all the information on the Site Collection will be secure, and only the Site Owners and all people who have permissions to the site can see the information inside and share the same. This account can be visible if we create an auditing for our Site Collection or personal site. All private information is safe and, nothing will be collected, as we said before this account only gets information for auditing and looks for possible virus attack.
Not in the slightest a helpful response *sigh* :(
no feedback yet from Microsoft Support.
Depressingly the norm for this issue...
Hey TonyRedmond,
Here's another juicy bit information, though I'd take with a grain of salt, as I've gathered some additional information on how this error is related to the new and old Delve entry points, see this thread: https://techcommunity.microsoft.com/t5/Delve/Anyone-also-seeing-app-sharepoint-com-in-Delve/m-p/34684/highlight/false#M209
Here's the latest support response:
Please know that I received updates from the Production Group, that specify the following:
“This is one System account, that normally is used when the customer sets up, one App, and provides that App a high level permission to run on the SharePoint Site. In this particular case, an App was probably created, or set up, or even for example a workflow and was given an Elevated Permission, on the SharePoint Site, and because of that, the account is shown as the last one that modified the documents. So the customer needs to look for all Apps he has on SharePoint, and see which one has this high level permission. This can be the reason that this account is showing up.”
In my case I don't have any additional apps allowed for the documents affected on that site, so I'm sure the statement is inaccurate.
This is getting pretty silly as the quality of the answers from support is now dubious at least and possibly misleading at worst.
It would be nice if someone like Dan Holme could throw light into this dark corner of Delve...
Well, fun fact, I just got a response, without asking for an update ;) Or maybe they've tread this thread, I don't know ;)
Here's the response:
I am sending this e-mail as I would like to reinforce that we are still investigating the issue that you’re currently experiencing with the Delve system account and working on finding a solution for it. We have engaged the Production Group and still waiting for an answer from them.
I would like to take the time to thank you for your patience and flexibility and assure you that I will revert back to you as soon as possible with a resolution.
TL;DR: still looking
