This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(44.800000000000004, 10%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMZ%3C/text%3E%3C/svg%3E)
We have previously created multiple Office 365 applications for the 2002 and 2008 releases in SCCM through OCT. Now I'm not able to do so when creating an application for the latest Semi Annual Enterprise release. When OCT loads I am able to choose "Microsoft 365 apps for enterprise" but it is not possible to choose a channel/version. Nothing happens when clicking it. I have tried with multiple user accounts on multiple computers with the same result. Does anyone else experience this?
I haven't had any issues.
If you're looking to create the XML, you could leverage this: https://config.office.com/deploymentsettings
If you're looking for some other M365 deployment ideas, you can check out this series: https://docs.recastsoftware.com/ConfigMgr-Docs/M365-Deployment-Series.html
It's weird though that it stopped working all of a sudden. We are on the latest SCCM version too with the latest hotfix.
We want SCCM to do the whole process including downloading the installation files, which doesn't happen if we just create the XML at config.office.com. I might try to create the XML there and then import it in the SCCM Office 365 Installer process. The hassle is that I cannot import an existing one and just change it at config.office.com, it has to be done from scratch.
Hello again,
It turns out that creating an XML on config.office.com and importing it works. But I also found out that my current XML files created my MECM can be re-used if I just delete the Version section of the XML, then the latest version in the channel specified will be selected automatically when clicking Review. It doesn't matter that I still cannot select a channel and version in the OCT GUI because I can still submit the XML in MECM and all the content is downloaded successfully to the file share.
Thank you for your input.
That process is's exactly what I've done up until now. The problem is that it is not possible to choose a channel/version in that tool, as stated in my original question.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(108.80000000000001, 31%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EWP%3C/text%3E%3C/svg%3E)
Just wanted to chime on this after experiencing it myself, I ended up fixing it by changing my outgoing source IP from a hosting IP to a residential IP (this is in my homelab where I have an external VPS handing routing to the servers in my house). I suspect Microsoft may be blacklisting VPS/hosting IPs.
It started working again when I deployed 2102 and 2108.
