Forum Discussion

Marc Lluís Lozano's avatar
Marc Lluís Lozano
Copper Contributor
Nov 08, 2017

Change the logo in Modern Team Site -- Strange behavour

Hi all,

 

I've been facing recently a problem with the modern Team Site where I was, weeks ago, able to change the logo using Powershell but now I got some strange behavour:

 

1) On "front-end" pages, like Site Contents or Home.aspx I get my custom logo but, after a second it's automatically replaced by the Default one.

 

2) On site information it's my custom logo there

 

3) On my backend pages, like Site Settings, it's the custom logo as well.

 

What is hapening here?

 

Can anyone help me please? Really appreciate.

 

Thanks,

 

Marc

11 Replies

  • TerranIncognito's avatar
    TerranIncognito
    Copper Contributor

    Hey Microsoft, logo rendering should not be rocket science. Corporate leadership does not like going to their sites and not seeing their company logo. This is a bad image for Microsoft...pun intended. Please get a team on this.

      • bcobra's avatar
        bcobra
        Copper Contributor
        Change the group icon via outlook to a new 64x64 icon. Delete the __siteIcon__ png and jpg files in your site assets library. The logo should now be pull the new group icon from exchange.
  • I would change the logo for the Group itself, rather than trying to apply it to the Team Site.

    • Marc Lluís Lozano's avatar
      Marc Lluís Lozano
      Copper Contributor

      Hi Hunter and thanks for your reply,

       

      I think the PnP command used when I create the team site:

      New-PnPUnifiedGroup -GroupLogoPath $logofilePath

      Sets the logo image for the whole group, not only for the team site page.

       

      Also when I apply some other branding customizations in the site I do this:

       

      Set-PnPUnifiedGroup -Identity $groupName -GroupLogoPath $logo

      So, in theory, this should change the Logo for the whole group as well.

       

      Thanks,

      • Hunter Willis's avatar
        Hunter Willis
        Iron Contributor

        Found this thread. This apparently used to be a bug across all of 365. Seems as though using a .jpg used to fix the issue, but also seems as though support was not super responsive to people having the error. 

         

        What is the file format you are using, and what is the size of the image?

Resources