I have currently had the burden of this annoying pop up box asking for credentials every so often in our office 2013 suite. I managed to get rid of it until the recent updates.

What i did in the past to get rid of it:

--Went into trust settings-> Trust Center Settings -> Privacy options and unchecked EVERYTHING.

That worked for awhile then it came back so then I:

--Went into regedit and set the UseOnlineContent to 0.

That worked for awhile and now after the recent office updates it has came back to haunt our office once again! Those who have had to deal with this in a work environment know it is very frustrating to have 100 end users email, call, and confront you about an issue you can't fix over and over again. NOT VERY FUN!

Any help is welcome.

Thanks for your time,

L DeWitt.

Hi L DeWitt,

As far as I know there are 3 methods for solving this issue, and you tried 2 methods of them.

One more method is to add the following sites as the exceptions of proxy server in IE:

officeimg.vo.msecnd.net

office.microsoft.com

odc.officeapps.live.com

Then you can refer to this link, this blog talk about a particular situation that open Office files from a web servera and get the Poexy Promt. You can also try this method, maybe it's helpful.

http://blogs.technet.com/b/office_integration__sharepoint/archive/2014/02/24/users-are-prompted-for-username-and-password-when-opening-an-office-file-from-a-web-server.aspx

Please try these methods and check if they are work for you. I'm glad to help and follow up your reply.

Regards,

Emi Zhang
TechNet Community Su

Thanks for the reply Emi,

I guess i forgot to mention I have put all those sites as exceptions to bypass our proxy server. What's weird is I am a PC Technician so my credentials have "all gates" meaning I don't have restrictions in our proxy. Although my traffic still goes through the proxy I am not bound by any restrictions and all sites are allowed for my domain account.

As for the link you've provided we don't use our office files on the web they are all stored locally or on a network share within our networks.

I've changed a bunch of registry objects to point to google and still no luck.