Forum Discussion
Sensitivity labels integration not working after latest update on Android & iOS
Same issue for us. After speaking with Microsoft365 support they've advised they can't help and that this needs to be raised via App support directly. I have raised a case, and I've been batting back and forth to questions like "have you spoken to your IT helpdesk", even though I've already given them a wealth of information regarding the implementation and their own documentation which highlights how this should function.
Hopefully several tickets might expediate a fix. The instructions that 365 support gave me were as follows:
Kindly raise a ticket with the in-app support for dedicated support.
1. To do so, please click on your profile picture at the top left corner of the page.
2. click on the question mark button at the bottom left.
3. click on contact Outlook mobile support.
4. under "how can we help", click on "other" at the bottom.
5. on the "other" page, click on "other" again.
6. describe the issue you are faced with giving details of the Outlook mobile app version and when the sensitivity label feature last worked.
7. submit the request.
- We've encountered this same issue. Since 4.24.13.0 on iOS/iPadOS & 4.24.13.1 on Android, any staff with later versions no longer have sensitivity labels enforced, or the ability to set a label. Office apps on mobile still enforce sensitivity labels, and Windows devices work as expected.
Has anyone in this post got to a resolution yet? We're in a situation where we might have to stop all staff using mobile devices for email.
Honestly, I think Microsoft need to roll back as we have evidence early versions of the apps are working.Organisation with labelling are a rare breed, organisations that enforce labelling are even rarer. This problem only prevents email for the organisations who enforce labelling, to those that "allow" labelling it's an inconvenience.
Given we're such a minority of the customer base and the lack of pressure that we create, I imagine it'll take quite some time for a fix to be implemented. I would suggest you raise a ticket to app support as per my previous post, the more noise we can make the better.I've just got an heads up from Microsoft:
Indeed right now we got the confirmation that we have started to receive similar complaints and our team is already working on it. I have recorded your case also to speed things up. Really appreciate your patience in the meantime.
