GPO requested: Suppress the "We've signed you in" prompt on first use

%3CLINGO-SUB%20id%3D%22lingo-sub-1539768%22%20slang%3D%22en-US%22%3EGPO%20requested%3A%20Suppress%20the%20%22We've%20signed%20you%20in%22%20prompt%20on%20first%20use%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1539768%22%20slang%3D%22en-US%22%3E%3CP%3ECurrently%20when%20Edge%20is%20launched%20for%20the%20first%20time%20there%20is%20a%20pop-up%20that%20says%20%22We've%20signed%20you%20in%22.%20I%20would%20like%20to%20be%20able%20to%20suppress%20this.%20In%20an%20Enterprise%20the%20users%20don't%20need%20to%20be%20told%20they%20are%20signed%20in%20as%20it%20will%20be%20forced%2Fnot%20optional.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1542423%22%20slang%3D%22en-US%22%3ERe%3A%20GPO%20requested%3A%20Suppress%20the%20%22We've%20signed%20you%20in%22%20prompt%20on%20first%20use%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1542423%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F446198%22%20target%3D%22_blank%22%3E%40kqf_chris%3C%2FA%3E%26nbsp%3BThanks%20for%20reaching%20out%3B%20that's%20a%20great%20point.%20I'll%20ask%20our%20Enterprise%20team%20and%20let%20you%20know%20if%20they%20have%20any%20insights%20to%20share.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CI%3EFawkes%20(they%2Fthem)%3CBR%20%2F%3EProgram%20Manager%20%26amp%3B%20Community%20Manager%20-%20Microsoft%20Edge%3CI%3E%3C%2FI%3E%3C%2FI%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1542722%22%20slang%3D%22en-US%22%3ERe%3A%20GPO%20requested%3A%20Suppress%20the%20%22We've%20signed%20you%20in%22%20prompt%20on%20first%20use%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1542722%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F446198%22%20target%3D%22_blank%22%3E%40kqf_chris%3C%2FA%3E%26nbsp%3BGood%20news%3A%20it%20sounds%20like%20you%20can%20easily%20disable%20that.%20If%20you%20enable%20the%20%22hide%20FRE%22%20policy%20along%20with%20either%20disabling%20sync%20or%20forcing%20sync%2C%20this%20popup%20will%20also%20be%20disabled.%26nbsp%3BHopefully%20that%20helps!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CI%3EFawkes%20(they%2Fthem)%3CBR%20%2F%3EProgram%20Manager%20%26amp%3B%20Community%20Manager%20-%20Microsoft%20Edge%3CI%3E%3C%2FI%3E%3C%2FI%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1553359%22%20slang%3D%22en-US%22%3ERe%3A%20GPO%20requested%3A%20Suppress%20the%20%22We've%20signed%20you%20in%22%20prompt%20on%20first%20use%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1553359%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F484598%22%20target%3D%22_blank%22%3E%40fawkes%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20Hide%20FRE%20set%20already%20with%20%22Configure%20whether%20a%20user%20always%20has%20a%20default%20profile%20automatically%20signed%20in...%22%20(not%20force%20sync%20because%20it%20doesn't%20exist%20yet).%20This%20window%20is%20the%20only%20one%20that%20pops%20up.%20Can%20you%20have%20someone%20take%20a%20look%20at%20this%20behavior%3F%20Thanks%20for%20your%20help!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1553322%22%20slang%3D%22en-US%22%3ERe%3A%20GPO%20requested%3A%20Suppress%20the%20%22We've%20signed%20you%20in%22%20prompt%20on%20first%20use%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1553322%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F484598%22%20target%3D%22_blank%22%3E%40fawkes%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20the%20following%20set%2C%20but%20still%20get%20the%20%22We've%20signed%20you%20in%22%20prompt%20on%20first%20use%3A%3C%2FP%3E%3CUL%3E%3CLI%3EDisable%20synchronization%20of%20data%20using%20Microsoft%20sync%20services%3A%20%3CSTRONG%3EDisabled%3C%2FSTRONG%3E%3C%2FLI%3E%3CLI%3EConfigure%20whether%20a%20user%20always%20has%20a%20default%20profile%20automatically%20signed%20in%20with%20their%20work%20or%20school%20account%3A%20%3CSTRONG%3EEnabled%3C%2FSTRONG%3E%3C%2FLI%3E%3CLI%3EHide%20the%20First-run%20experience%20and%20splash%20screen%3A%20%3CSTRONG%3EEnabled%3C%2FSTRONG%3E%3C%2FLI%3E%3CLI%3EBrowser%20sign-in%20settings%3A%20%3CSTRONG%3EEnabled%2C%20Force%20users%20to%20sign-in%20to%20use%20the%20browser%3C%2FSTRONG%3E%3C%2FLI%3E%3C%2FUL%3E%3CP%3EAlso%20looking%20for%20a%20way%20to%20suppress%20this.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1553478%22%20slang%3D%22en-US%22%3ERe%3A%20GPO%20requested%3A%20Suppress%20the%20%22We've%20signed%20you%20in%22%20prompt%20on%20first%20use%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1553478%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F743698%22%20target%3D%22_blank%22%3E%40mrbrown38%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20DOES%20supress%20the%20message%20if%20I%20set%3C%2FP%3E%3CUL%3E%3CLI%3E%3CSPAN%3EBrowser%20sign-in%20settings%3A%26nbsp%3B%3CSTRONG%3EEnabled%2C%20Disable%20browser%20sign-in%20%3C%2FSTRONG%3E(vs%20forced%20sign-in).%3C%2FSPAN%3E%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EMy%20end%20goal%20is%20for%20the%20sign-in%20to%20be%20forced%2C%20but%20suppress%26nbsp%3Bthe%20message%20that%20they've%20been%20signed%20in.%20While%20we%20aren't%20syncing%20with%20Azure%20currently%2C%20the%20goal%20will%20be%20to%20in%20the%20future.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1559395%22%20slang%3D%22en-US%22%3ERe%3A%20GPO%20requested%3A%20Suppress%20the%20%22We've%20signed%20you%20in%22%20prompt%20on%20first%20use%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1559395%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F743698%22%20target%3D%22_blank%22%3E%40mrbrown38%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EExactly%20where%20I'm%20at.%20IT%20department%20has%20sync%20as%20we%20are%20the%20guinea%20pigs.%20Before%20that%20it%20was%20disabled%20--%20no%20prompt%20obviously.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1564132%22%20slang%3D%22en-US%22%3ERe%3A%20GPO%20requested%3A%20Suppress%20the%20%22We've%20signed%20you%20in%22%20prompt%20on%20first%20use%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1564132%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F446198%22%20target%3D%22_blank%22%3E%40kqf_chris%3C%2FA%3E%26nbsp%3Band%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F743698%22%20target%3D%22_blank%22%3E%40mrbrown38%3C%2FA%3E%26nbsp%3BI%20followed%20up%20with%20the%20team%20and%20got%20some%20clarification.%20You%20were%20correct%3B%20it%20sounds%20like%20this%20policy%20isn't%20fully%20rolled%20out%20yet%2C%20so%20stay%20tuned%20for%20that%20in%20the%20near%20future!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CI%3EFawkes%20(they%2Fthem)%3CBR%20%2F%3EProgram%20Manager%20%26amp%3B%20Community%20Manager%20-%20Microsoft%20Edge%3CI%3E%3C%2FI%3E%3C%2FI%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1566718%22%20slang%3D%22en-US%22%3ERe%3A%20GPO%20requested%3A%20Suppress%20the%20%22We've%20signed%20you%20in%22%20prompt%20on%20first%20use%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1566718%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F484598%22%20target%3D%22_blank%22%3E%40fawkes%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDoes%20it%20mean%2C%20that%20in%20near%20future%20there%20will%20be%20a%20policy%20which%20will%20basically%20force%20users%20to%20sync.%26nbsp%3B%3C%2FP%3E%3CP%3EFor%20us%20it%20would%20be%20really%20great%20as%20this%20way%20we%20don't%20need%20to%20care%20for%20backing%20up%20users%20bookmarks%20and%20so%20on.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1566911%22%20slang%3D%22en-US%22%3ERe%3A%20GPO%20requested%3A%20Suppress%20the%20%22We've%20signed%20you%20in%22%20prompt%20on%20first%20use%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1566911%22%20slang%3D%22en-US%22%3EExactly.%20We%20still%20get%20call%20to%20the%20ServiceDesk%20with%20users%20who%20want%20to%20be%20helped%20with%20that%20since%20the%20y%20don't%20understand%20the%20FRE.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1638010%22%20slang%3D%22en-US%22%3ERe%3A%20GPO%20requested%3A%20Suppress%20the%20%22We've%20signed%20you%20in%22%20prompt%20on%20first%20use%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1638010%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F743698%22%20target%3D%22_blank%22%3E%40mrbrown38%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CUL%3E%3CLI%3EHide%20the%20First-run%20experience%20and%20splash%20screen%3A%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3EEnabled%2C%3C%2FLI%3E%3CLI%3EAbove%20that%20Disable%20synchronization%20of%20data%20using%20Microsoft%20sync%20services%3A%3CSPAN%3E%26nbsp%3BMake%20it%20%3CSTRONG%3EEnabled%3C%2FSTRONG%3E%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3EThis%20is%20required%20foe%20Windows%208%20Systems%2C%20Since%20that%20functionality%20may%20not%20be%20there.%3C%2FLI%3E%3CLI%3EThis%20setting%20is%20not%20required%20for%20windows%2010%2C%26nbsp%3BHide%20the%20First-run%20experience%20and%20splash%20screen%20is%20enough.%3C%2FLI%3E%3C%2FUL%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1670335%22%20slang%3D%22en-US%22%3ERe%3A%20GPO%20requested%3A%20Suppress%20the%20%22We've%20signed%20you%20in%22%20prompt%20on%20first%20use%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1670335%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F484598%22%20target%3D%22_blank%22%3E%40fawkes%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20trying%20to%20implement%20the%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployedge%2Fmicrosoft-edge-on-premises-sync%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EOn-premise%20sync%3C%2FA%3E%20and%20will%20need%20to%20suppress%20this%20prompt.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20prompt%20is%20confusing%20for%20users%20because%20it%20states%20%22Sync%20isn't%20available%20for%20this%20account%2C%22%20yet%20the%20reason%20we%20are%20forcing%20AD%20automatic%20sign-in%20is%20to%20support%20the%20On-premise%20sync.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20expect%20this%20would%20drive%20a%20number%20of%20support%20calls%20requiring%20explaining%20to%20users%20that%2C%20indeed%2C%20their%20bookmarks%20will%20be%20synced.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1693543%22%20slang%3D%22en-US%22%3ERe%3A%20GPO%20requested%3A%20Suppress%20the%20%22We've%20signed%20you%20in%22%20prompt%20on%20first%20use%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1693543%22%20slang%3D%22en-US%22%3E%3CP%3EFollowing%20this%20thread.%26nbsp%3B%20I%20too%20would%20love%20to%20suppress%20this%20message.%26nbsp%3B%20We're%20starting%20to%20test%20the%20on-premise%20sync.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1700901%22%20slang%3D%22en-US%22%3ERe%3A%20GPO%20requested%3A%20Suppress%20the%20%22We've%20signed%20you%20in%22%20prompt%20on%20first%20use%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1700901%22%20slang%3D%22en-US%22%3E%3CP%3EAny%20progress%20on%20this%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20also%20wanting%20to%20inpliment%20syncronisation%20on%20premise%20but%20that%20window%20is%20very%20counter-intuative%2C%20we%20dont%20want%20to%20show%20that%20screen%20and%20whats%20even%20worse%20is%20that%20the%20information%20is%20wrong%20as%20it%20says%20syncronization%20is%20not%20avaiable%2C%20where%20it%20in%20fact%20is%20what%20we%20are%20indeed%20enableing%20for%20our%20users%2C%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Contributor

Currently when Edge is launched for the first time there is a pop-up that says "We've signed you in". I would like to be able to suppress this. In an Enterprise the users don't need to be told they are signed in as it will be forced/not optional.

 

Thanks!

14 Replies
Highlighted

@kqf_chris Thanks for reaching out; that's a great point. I'll ask our Enterprise team and let you know if they have any insights to share.

 

Fawkes (they/them)
Program Manager & Community Manager - Microsoft Edge

Highlighted

@kqf_chris Good news: it sounds like you can easily disable that. If you enable the "hide FRE" policy along with either disabling sync or forcing sync, this popup will also be disabled. Hopefully that helps!

 

Fawkes (they/them)
Program Manager & Community Manager - Microsoft Edge

Highlighted

@fawkes 

I have the following set, but still get the "We've signed you in" prompt on first use:

  • Disable synchronization of data using Microsoft sync services: Disabled
  • Configure whether a user always has a default profile automatically signed in with their work or school account: Enabled
  • Hide the First-run experience and splash screen: Enabled
  • Browser sign-in settings: Enabled, Force users to sign-in to use the browser

Also looking for a way to suppress this.

Highlighted

@fawkes

 

I have Hide FRE set already with "Configure whether a user always has a default profile automatically signed in..." (not force sync because it doesn't exist yet). This window is the only one that pops up. Can you have someone take a look at this behavior? Thanks for your help!

Highlighted

@mrbrown38 

It DOES supress the message if I set

  • Browser sign-in settings: Enabled, Disable browser sign-in (vs forced sign-in).

 

My end goal is for the sign-in to be forced, but suppress the message that they've been signed in. While we aren't syncing with Azure currently, the goal will be to in the future.

Highlighted

@mrbrown38 

Exactly where I'm at. IT department has sync as we are the guinea pigs. Before that it was disabled -- no prompt obviously.

Highlighted

@kqf_chris and @mrbrown38 I followed up with the team and got some clarification. You were correct; it sounds like this policy isn't fully rolled out yet, so stay tuned for that in the near future!

 

Fawkes (they/them)
Program Manager & Community Manager - Microsoft Edge
 

Highlighted

Hello @fawkes 

Does it mean, that in near future there will be a policy which will basically force users to sync. 

For us it would be really great as this way we don't need to care for backing up users bookmarks and so on.

Highlighted
Exactly. We still get call to the ServiceDesk with users who want to be helped with that since the y don't understand the FRE.
Highlighted

@mrbrown38 

  • Hide the First-run experience and splash screen: Enabled,
  • Above that Disable synchronization of data using Microsoft sync services: Make it Enabled
  • This is required foe Windows 8 Systems, Since that functionality may not be there.
  • This setting is not required for windows 10, Hide the First-run experience and splash screen is enough.
Highlighted

@fawkes 

 

We are trying to implement the On-premise sync and will need to suppress this prompt.

 

The prompt is confusing for users because it states "Sync isn't available for this account," yet the reason we are forcing AD automatic sign-in is to support the On-premise sync.

 

We expect this would drive a number of support calls requiring explaining to users that, indeed, their bookmarks will be synced.

 

Highlighted

Following this thread.  I too would love to suppress this message.  We're starting to test the on-premise sync.

Highlighted

Any progress on this?

 

We are also wanting to inpliment syncronisation on premise but that window is very counter-intuative, we dont want to show that screen and whats even worse is that the information is wrong as it says syncronization is not avaiable, where it in fact is what we are indeed enableing for our users, 

Highlighted

@fawkes  Hi did you get any insight into when this might be fully implemented ? Thanks