Forum Discussion

RS_Admin's avatar
RS_Admin
Brass Contributor
Apr 02, 2024
Solved

General Question: Microsoft 365 admin console tab label

I've never noticed before, but I do now. My admin tab label in any browser I choose, across several networks, displays as "Početak - Microsoft 365 admin center" via login through https://portal.microsoft.com

 

I am not Serbian, my company has no affiliations with Serbia, and our regional settings are not Serbian. Yet, that "Početak" is the word for "beginning" in Serbian. I'm thinking maybe Serbian contractors or Microsoft devs maybe made a mistake? I cannot find anything relevant to this via searches, so maybe someone has an answer on here. Maybe I'm overthinking, but just curious. I'm also not a developer, so the answer might be something very innocent.

 

<*UPDATE 4/4/24*- Microsft appears to be rolling out a fix either regionally or all together. NA tenants look to be getting attention (ours is displaying correctly now). Looks like this was simply a language mishap, as pointed out in the noted "best response" in this thread. Thanks all for the interest and getting this noticed! >

  • Admin.microsoft.com uses resources hosted on res.cdn.office.net for those tab titles. In this case, that request looks like this:

    GET https://res.cdn.office.net/admincenter/admin-pkg/2024.3.28.1/en/jsc/reactadminbootstrap.js HTTP/1.1
    Host: res.cdn.office.net
    Connection: keep-alive
    sec-ch-ua: "Microsoft Edge";v="123", "Not:A-Brand";v="8", "Chromium";v="123"
    sec-ch-ua-mobile: ?0
    User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/123.0.0.0 Safari/537.36 Edg/123.0.0.0
    sec-ch-ua-platform: "Windows"
    Accept: */*
    Sec-Fetch-Site: cross-site
    Sec-Fetch-Mode: no-cors
    Sec-Fetch-Dest: script
    Referer: https://admin.microsoft.com/
    Accept-Encoding: gzip, deflate, br, zstd
    Accept-Language: en-US,en;q=0.9

    Although the path contains "en" as the lang code, the strings are (as everyone noted) in Croatian. All the other locales I tested (it, de, etc.) don't appear to have the same bug. Just "en." Also, res.cdn.office.net uses Akamai as a content delivery network, and this .js file is cached with Cache-Control max-age=630720000 (20 years?). So even if it was fixed on the origin servers, the Akamai cache would have to be purged, or they would have to use a new file path, and that appears to be their approach (this one has the release date /2024.3.28.1/ in the path).

    This has already been confirmed to be a bug that Microsoft is working on by other members, I just wanted to provide some additional details based on what I see.

Resources