Restart Office to apply changes to your privacy settings - endless notices

I spoke too soon.... :(

The "prompt" is popping up when I sign on, while I'm scrolling mail (from any email accountnot just gmail), and while I'm reading emails from a yahoo groups account or an AOL account. It's as though it's timed to pop up every 30 seconds no matter what I'm doing in Outlookwriting or reading emails.

I did figure out how to get rid of OneDrive Personal, but it say that if I do that, I can't access emoji's while composing mail in Outlook, access pictures from the Web while in Word or Outlook, and basically have no access to any internet features in any Office 365 programs. So, I'm either stuck with useless programs that are bare bones, or I give up all privacy. And, either way, I STILL keep getting the pop-up prompt for my Google email and password every 30 seconds.

This issue became a problem for me right after I had to reinstall office on a freshly installed Windows 10 Pro.  I have only started troubleshooting, this morning, but I'm guessing this has to do with "connected services" at one or more levels, locations, etc. 

The required reboot is also an indicator to review your privacy settings, as well as any changes Microsoft has made to a particular Office service's privacy policy, since the last time you opened the Office application.

With all of the possible "connected services" that exist across multiple Office components, and with the present generation of MS developers' propensity to tweak their application(s), then boot them out to us in an essentially alpha development stage, it's no wonder this is happening on a nearly a daily basis.

I hear people saying, "but I don't have "connected services" enabled.  Well, that may be true of yesterday, but each and every update (not just the announced ones) carries with it a probability that your privacy settings get changed, especially when the updates have directly related changes to "connected services." 

The only way to move "alpha-stage" services through a development cycle is to rigorously test them.  For a "connected service" to get tested, it needs to be utilized, and to get it utilized requires end users to use it.  That's not gonna happen in a timely manner when a very significant number of end users have these "connected services" turned off.  This is only going to get more common.

I'm making this observation based on my past application developer experience with a Fortune 500 corporation.  I believe we won't hear directly from Microsoft because they're the ones surreptitiously turning our "connected services" back on.  Then, when we reboot without reading MS' updated privacy policy, we just gave them permission to leave the privacy setting as they just got reconfigured.

For me, privacy isn't so much the issue.  The problem is that every software company wants at least some of my metadata, and if I approve them all, it buries almost any hope of tracing rogue, outbound firewall traffic, should I need to determine if there is malware loose on my network.

Privacy was dead over 10 years ago . . .

...and this right here is the most horrible decision for a monopoly company to make. The instant they revert settings the user has consciously made, grabbing private data in the process, is when people might just wake up from their slumber of stupid. And Office isn't even "free" software, which usually is the part of the equation that justifies an unashamed abuse of power.

I agree, and I'm still speculating about how this is exactly working because I haven't yet received the notice again so that I can drill deeper.  My hunch is they are getting around this by changing the privacy setting as a part of the reboot.  I'm pretty sure there will be a way to avoid their intentions, but it will be obscure and annoying and time-consuming to do so.

I think the issue with frequency has to do with Office development being spread across numerous MS development teams, who then compete internally, leaving the end-users to suffer their impetuous tweaking.  On the other hand I'm old and cranky about all this, and I could be wrong, but not totally so...

The worst of all is that with the end of Windows 8.1 (except Enterprise editions) a dedicated, MS beta testing department pretty much disappeared.  The consumer now does the beta-testing; some voluntary with pre-releases, the remainder by proxy of the fact the software has been just plain buggy when released.  However, I've noticed much improvement in just the last 2 years, in relation to Windows 10.

Possibly, the worst-case of forced, end-user labor has become the iOS platform.

Sorry but I'm not interested in Office analyzing my content so won't allow this.

Ditto

Double-Ditto.