Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hi, we are trying to integrate our Microsoft Endpoint Manager (previously Intune) into Cisco ISE 3.1 Patch 3 as external MDM-server, but it always returns API version 2 instead of version 3 when testing connection. The documentation says version 3 is...
Yes, correct. Changing the "Instance name" manually from a working auto-discover was the only real thing I needed to do, as port is 443 by default, and then click "Test connection". Then it would report APIv3 support and I was able to turn on SAN GUI...
Very nice find, @bart.t !This has solved the problem for us. Here is the steps I used to get it to work:I first tried adding manual server, by using "fef.manage.microsoft.com" as server (which in my case resolved to "fef.msub06.manage.microsoft.com",...
@bart.t Unfortunately the case progress has been very slow. After a lot of ISE log debugging, Cisco redirected us to Microsoft to verify that "version 3" is active and being sent, and then Intune support just redirect us to the integration guide and ...
Hi.We can't adjust the settings for Device Identifier, since it only says that it supports API V2 (greyed out).See the screenshots for our settings. I have removed client ID and Token Issuing URL in the picture only. They are correctly filled out in ...
