Account-Driven Device Enrollment for iPadOS 18.2

Question

Created Dec ’24

Replies 3

Boosts 0

Participants 4

Hi, I'm glad to hear that the service discovery process is improved on iOS/iPadOS 18.2 mentioned here. https://support.apple.com/en-ca/guide/deployment/dep4d9e9cd26/1/web/1.0

I tried it on my development MDM server.

Set default MDM for iPad to my development MDM server on Apple Business Manager.
Call the new API https://developer.apple.com/documentation/devicemanagement/account_driven_enrollment_profile and 200 OK is returned

However the service discovery fails with the following error.

 Invalid well-known response for https://{my email's comain name}/.well-known/com.apple.remotemanagement?user-identifier={my email}&model-family=iPad: <NSHTTPURLResponse: 0x300a9f420>
Invalid well-known response for https://axm-servicediscovery.apple.com/mdmBaseURL?user-identifier={my email}&model-family=iPad: <NSHTTPURLResponse: 0x3009047a0>

It seems fallback process to https://axm-servicediscovery.apple.com/mdmBaseURL actually works but it returns 404 Not Found error.

How can we use this awesome feature? Thank you :)

Boost

Answer 1

Device Management Engineer OP

Apple

Jan ’25

Please file a bug report for this, and include the domain name used for your org.

0

Answer 2

DTS Engineer OP

Apple

Feb ’25

Information for filing a bug report:

Bug Reporting: How and Why? has tips on creating your bug report.

0

Answer 3

PrathikG OP

2w

Were you able to figure this out? I have tried setting up service discovery using https://developer.apple.com/documentation/devicemanagement/assign-account-driven-enrollment-profile?language=objc and tried accessing the email domain and see the same error as above

 Service URL from wellknown URL request finished with data: 2 bytes, response: <NSHTTPURLResponse: 0x30198e860> { URL: https://axm-servicediscovery.apple.com/mdmBaseURL?user-identifier=<email>&model-family=iPhone } { Status Code: 404, Headers {
    "Content-Encoding" =     (
        gzip
    );
    "Content-Length" =     (
        28
    );
    Date =     (
        "Wed, 19 Mar 2025 22:27:41 GMT"
    );
    Server =     (
        Apple
    );
    "Strict-Transport-Security" =     (
        "max-age=31536000; includeSubdomains"
    );
    Vary =     (
        "content-encoding"
    );
    "x-apple-request-uuid" =     (
        "e930d24c-06d1-429d-a367-28c8cd6b1080"
    );
    "x-content-type-options" =     (
        nosniff
    );
    "x-frame-options" =     (
        SAMEORIGIN
    );
    "x-xss-protection" =     (
        "1; mode=block"
    );
} }

0

	Invalid well-known response for https://{my email's comain name}/.well-known/com.apple.remotemanagement?user-identifier={my email}&model-family=iPad: <NSHTTPURLResponse: 0x300a9f420>
	Invalid well-known response for https://axm-servicediscovery.apple.com/mdmBaseURL?user-identifier={my email}&model-family=iPad: <NSHTTPURLResponse: 0x3009047a0>

	Service URL from wellknown URL request finished with data: 2 bytes, response: <NSHTTPURLResponse: 0x30198e860> { URL: https://axm-servicediscovery.apple.com/mdmBaseURL?user-identifier=<email>&model-family=iPhone } { Status Code: 404, Headers {
	"Content-Encoding" = (
	gzip
	);
	"Content-Length" = (
	28
	);
	Date = (
	"Wed, 19 Mar 2025 22:27:41 GMT"
	);
	Server = (
	Apple
	);
	"Strict-Transport-Security" = (
	"max-age=31536000; includeSubdomains"
	);
	Vary = (
	"content-encoding"
	);
	"x-apple-request-uuid" = (
	"e930d24c-06d1-429d-a367-28c8cd6b1080"
	);
	"x-content-type-options" = (
	nosniff
	);
	"x-frame-options" = (
	SAMEORIGIN
	);
	"x-xss-protection" = (
	"1; mode=block"
	);
	} }