Cannot modify Azure AD / 365 Login Branding

Adam C 26 Reputation points
2022-02-15T17:37:03.66+00:00

I've already been through the rigmarole with the Azure team on this, who tell me I need a 'paid' Azure subscription for it to be investigated.. but here goes.

As we do with EVERY client, we got round to customising our own internal 365 tenant's logo/custom branding in the Azure AD Admin portal.

To clarify I'm in;
365 Admin Center > Azure AD Portal > Azure Active Directory > 'Company Branding'.

So far, so good. Click on the 'Default' entry and attempt to upload images, 1920x1080px - Yup. <300kb - Yup.

Then comes the error....
174631-image.png

I cannot replicate this issue on ANY other 365 tenant. I am signed in as a global admin with every role possible, I've got an Azure AD P1 license attached to this user and I'm using the same set of images for the sign-in page background than I did on the other 3 tenants I've tried. Never seen this before, I can't replicate it on a brand new tenant with exactly the same licensing/setup, therefore I'm left with it being a 365/platform issue, but that's it... This should be a 30 second job but is turning into a massive pain.

Windows 365 Business
Microsoft Entra
0 comments
Accepted answer
  1. Marilee Turscak-MSFT 36,846 Reputation points Microsoft Employee
    2022-02-17T15:25:08.53+00:00

    Hi @Adam C ,

    I filed a bug, captured the network logs, and reproduced the issue over a call with someone from the product team.

    I just tested again and it appears to be working for me as well as for another engineer who was having the same issue. It looks like it's possibly fixed, though I see that the bug is still open.

    Could you try again?

    EDIT:
    The bug is now closed as the issue was mitigated at 11PM PST last night (2/16).

    0 comments

8 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Adam C 26 Reputation points
    2022-02-15T22:14:05.027+00:00

    Thank you for the reply @Marilee Turscak-MSFT - I spent 45 minutes on the phone to Microsoft support and 25 minutes on a live chat, only to be told I need a paid Azure support subscription in order for them to even look into the issue. We didn't have any branding when I attempted this for what it's worth!

  2. Adam C 26 Reputation points
    2022-02-16T12:58:23.46+00:00

    Still not functioning today. I am not prepared to pay for an 'advanced' Azure subscription to fix a platform issue, I don't think that's unreasonable!

  3. Adam C 26 Reputation points
    2022-02-17T15:21:39.517+00:00

    Thank you for all of your replies. This reinforces the fact it's a platform issue, not specific to our tenant (Which I kinda already knew, but appreciated nonetheless).

    0 comments
  4. Adam C 26 Reputation points
    2022-02-17T15:27:02.76+00:00

    @Marilee Turscak-MSFT Is it being listed publicly as a bug anywhere I can reference? TIA

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.