Forum Discussion
Intune now showing tenant name on lockscreen
Hi everyone,
As of some weeks, Intune started showing the tenant name on the lockscreen. Where it used to say "this device belongs to your organisation" it now says: " This device belongs to company name" .
Since this is a big no for most of our customers, I was wondering if other people noticed this as well and maybe even found a solution for it. Microsoft support admitted that they changed this, but they will now help us getting it fixed or even giving us the option to enable or disable this.
Showing the company name on a device can make a device more interesting to people who might find a lost or stolen device. Therefore, we never show company names or logo's on the lock screen. And most customers we work with expect that kind of behaviour. We currently have to project on hold because if this detail. (And its costing us extra business because they are not buying the hardware that comes with it 😅)
I hope someone else is having more luck! In the meantime I'm escalating this via other companies in our group with better MS connections but those take some time.
And if you haven't noticed this issue, please be aware of it. As far as we know, only Intune has done this. Knox, Workspace one and Mobile Iron are not showing this message. Samsung has replied that this is absolutly not right in their opinion. Its a big risk for companies.
Hey Michel,
I hope you are doing well, and thanks for sharing.
My immediate thought here is whether the 'Lock screen messages policy' setting in Intune might override this? It sounds like you are on the road to getting this fixed so I imagine you have tried many options here.
Are any others experiencing this?
Thanks again,
LizzieThat is unfortunate to hear this was pushed out to your devices unannounced by Intune and you have no obvious way of reversing it. I use SOTI MobiControl primarily and it has a configuration script where you can set a custom lockscreen message to be whatever you want. You can also pass in Macros / dynamic variable names and have those resolved automatically to have customizations of the message per device. This feature has been around for quite some time as I've been using it since at least early 2022.
This is the script format that works in SOTI for reference.
writeprivateprofstring LockScreenString Message %DEVICENAME%
apply LockScreenString
Maybe you'll get lucky and Intune will have something similar.
Hi mattdermody , Lizzie ,
Thanks for suggesting this! We have tested this, it was my first guess as well. But when configuring this option in Intune, it adds the text below the " This devices belongs to companyX" text. It does not replace it.
This would have been the easiest solution haha
We are working with MS premier support, hopefully they do accept that this isnt the best choice and will make some changes.
Hi all,
Small update from my side.
Microsoft confirmed the issue, but keep saying its Google's fault. And keep answering in either copilot generated emails or with tips and tricks that have nothing to do with the actual issue.
We are trying to escalate things via Microsoft and Samsung, but keep running into dead ends.
Lizzie , did you happen to get a response?
Hey Michel,
even the behavior of what mattdermody mentioned about the Soti script behaves similar to what you see.
Just tested on one of our devices, it shows then a text changing between the devicename and the message "this device belongs to your organisation". And this is an Android 14 device, so nothing old.
Maybe make MS aware of that other MDM's don't see this issue and that this seem to be isolated to Intune (again).
Thanks for testing and confirming, very helpfull! We don't have acces to Soti but have acces to Intune, Knox Manage, Workspace One and Mobile Iron and all of them work as we want.
Samsung suggested configuring a device with just AMAPI, to see if that was the issue but that wasn't the case.
We have made MS aware of all of these tests, with lots of screenshots, but their response is terrible. They don't read what we are saying and forwarding Google discussion forms regarding removing the " this devices belongs to your company" line, not changing it like MS did somehow.
Its soooo frustrating haha
Have you tried setting a custom message?
Yes we have, it adds a line below the text " This device is managed by companyX", it does not replace it.
We spoke to an escalation team last friday, they acknowledge the issue and keep pointing fingers to Google. Going round in circles.
On a positive note, we have filed another ticket with Microsoft via another route and there we got confirmation that they will check with the Intune developers to see if something could be done.
Hey everyone,
I've been looking into this further and I've been following up with our engineering internally. I can confirm our team is working with Microsoft on this. I don't currently have an estimated timeline, but wanted to let you know that there is work on-going.
I hope this helps and I'll keep you posted if I receive more updates.
Thanks,
Lizzie
This helps, thanks lizzy!
In the meantime I have Microsoft support confirming that it was a change done by the Intune team, but I have no idea why they did this. Support is assisting in logging a design change request.
Microsoft support has applied a fix to our tenant which works. They can apply this fix to the tenants we want, so our customers are helped with this.
In the meantime Microsoft confirmed working with Google to see if this can be fixed, but not sure if this will be implemented. I still believe they don't really see the problem.
Is it Google or Microsoft who do not see this as a problem.
We do not care so much about this but I can also send a case but if you have the casenumber from MS, I can reference it to your case.
There is no need to further escalate this, but thanks for offering!
I don't know who is at fault here. Microsoft says, and keeps saying, it has to do with a change on Google's side. But Intune is the only one displaying this issue as far as we could compare with other MDM solutions. Thats why we are looking at microsoft for fixing this.
And they did, with a little help from Lizzie !
