Intune – Send Custom Notifications – but not to too many people

I’ve been wrestling back and forth with Microsoft on this for the past few weeks. I’m able to use Intune’s “Send Custom Notifications” feature to send messages to a very small number of people.

But, recently, I wanted to notify just under a couple of hundred of my users that the version of iOS they are running will no longer be supported by my system. I thought this notification feature would be a neat way to reach out directly to them so they knew that I meant *them* specifically and not *them* generically as tends to happen with email communication of this sort.

So I sent my notification to a tiny number of people (me especially) to ensure that the message being sent looks good for the target folks on the mobile platform. Works fine.

Sent the identical message to a single group of 171 people (again, including me) and… nothing.
The next day I sent it again after confirming that, not only did none of my half dozen test mobile devices receive it, but NOBODY received it. And… again… nothing. This time I verified that the resulting Intune notification (bell at the top in Intune) confirmed “Success”.
Sent another notification to just myself and a coworker and…. works just fine.

Well… crap. So I sent off an email instead to the users to give them their warning and opened a ticket with Microsoft regarding this.

Basically Microsoft is telling me that I must have missed the dozen or so notifications across my devices, as did all of my users. They took pains to explain to me how end users sometimes don’t notice notifications when they come up and that must be the situation… on both days.

Long and short it turns out that there is no real auditing or logging of this feature so Microsoft cannot tell the notification disposition beyond the original “Success” which apparently only means Intune has acknowledged that I’ve submitted the request.

I wanted to put this warning out to you. Not only should you not be using this feature for time-sensitive information, but also there appears to be a threshold number of people – certainly in my case – to whom it can be sent before it will give up the ghost and just not do anything.

Be absolutely certain to include yourself and some sympathetic coworkers on ANY Intune Custom notification that you send out if you want to have any assurance that it actually made it to your audience.

In my opinion Microsoft needs to update this feature so it:

  1. Logs all sent messages,
  2. Provides a disposition for the message as to whether or not a device has acknowledged receiving it.

I don’t imagine there is a lot more I could ask for. The end user is welcome to ignore the message after delivery. At that point my goal has been achieved.

I would be interested to know if there are any other folks who have run up against this issue.

So my Tesla Model X has a Little Known Bug

Back in early December (2019) I noticed that the regen on my Tesla was not what it should be.

Basically, after overnighting in my garage on a 63 degree F morning, it would take about 25 minutes of my 40+ minute commute before I had full regeneration restored.

On a cooler 37 degree night, I ended up preheating the car for *54* minutes (miscalculated departure time) and, for that 32 minute drive I NEVER regained my full regen.

I contacted Tesla to have them take a look-see, after all, not a couple of weeks earlier they had replaced my Battery Coolant Heater (coincidence?).

Regardless, in spite of what seems like an obvious connection between a battery coolant heater and my battery heater not activating properly, Tesla came back and initially informed me basically that “battery packs are big and can be slow to warm up” and, when that didn’t work they then let me know that there is a firmware bug that is preventing the battery heater from activating.

Below is the transcript of my conversation with Tesla. I’m still waiting for the “future firmware update”.

Basically I’m seeing that Tesla Model X (Premium car) has now become so niche that it basically is not getting much attention at all. And I frankly believe that Tesla service is so overwhelmed that they can’t spend the time on customers such as myself, the earlier adopters who helped to fund the whole enterprise, to ensure that our vehicles are running correctly.

Color me disappointed. I can’t wait to see where I end up on the list of HW 3 upgrade recipients.

Tesla’s explanation of my Regen issue