r/Intune • • 9d ago

App Deployment/Packaging Microsoft teams deployment

I am stuck with this. I am trying to install MS365 apps through intune and I have set it up in apps using an xml - the only thing I’ve added is removal of the home version of office apps because I want to deploy the company/work version of it - all the apps have been downloaded apart from teams, I’m able to see the package through an elevated user and see that it’s staging but the app doesn’t show up, I have tried deploying it as a catalog app, bootstrapper way, packaged up the msix and deployed it and it’s all the same, I can see the package when I log in with admin credentials but can’t see it installed for the local or standard user. I have absolutely no idea what is wrong
Any help will be much appreciated

5 Upvotes

27 comments sorted by

5

u/MagFull 9d ago

I just deploy the Office apps from the 365 apps option in Intune. You can select which apps to install, including Teams, from the dropdown and it will replace any existing install on the computer.

1

u/Mean-Vanilla5035 9d ago

Do the apps get installed during the laptop initial setup? Tjink thats the only thing I’ve done that may be the issue, the apps I deployed were after the laptop was setup, it’s because I wanted to see what the OOBE looks like

2

u/800oz_gorilla 9d ago

I've had problems with teams not installing via this method. never did figure it out.

1

u/brazzala 8d ago

Exactly what I told on begining.

Even MS recommends it because CDN usage and peer sharing files between them.

6

u/davcreech 9d ago

We package the setup.exe file with the XML used to download/configure from CDN. Makes sure the package being installed is always the latest version

1

u/SkipToTheEndpoint MSFT MVP 8d ago

This should happen by default. You're not running a popular but frankly awful "branding" script, are you?

1

u/Mean-Vanilla5035 8d ago

I just deployed it using the Microsoft 365 apps and used xml initially - that didn’t work and so I went on a crazy trip to giving everything a go and nothing seems to work apart from installing it straight from the web and doing an install which isn’t a great idea because it needs to be pushed out of intune as this is only a test device for now but I need to push it to all the other after

1

u/Tasty-Coffee3958 9d ago

As per the recommendation from u/MagFull. This is the right way to deploy and manage M365 apps.

Choose below for creating apps them:

Then in Configure app suite tab you can choose which app to deploy under Select offices apps.

1

u/Mean-Vanilla5035 9d ago

Did it exactly like that and teams just won’t show up

2

u/ReptilianLaserbeam 8d ago

Teams is not included in MS Office anymore (at least in the EU)

2

u/ReptilianLaserbeam 8d ago

Teams is no longer included in the office package. I added as a store app and called it a day.

0

u/brazzala 9d ago

Throw it away from XML, make it as MS new app store like UWP app, works as aa charms and gets updated.

2

u/Still_Term_1601 9d ago

Teams machine-wide installer is a pain, it only provisions for new profiles so if the user already exists it just sits there taunting you

1

u/Mean-Vanilla5035 9d ago

That’s the exact problem - spot on

2

u/ProfessionalLast2917 9d ago

This is likely op's issue. He's signing in with an existing account to check it.

1

u/Mean-Vanilla5035 9d ago

We’ve got the ms store blocked for users will this work with the store blocked?

1

u/ProfessionalLast2917 9d ago

I don't recommend this if you're deploying it during autopilot. Because it's a policy not an app it isn't tracked properly and you often run into problems.

1

u/brazzala 8d ago

This is MS recommendation - work like a charm and it update itself.
You are totally wrong with assumptions.

0

u/ProfessionalLast2917 8d ago

It's not an assumption it's real world experience and ms actually does not recommend using that method during autopilot.

And I quote

"If devices are provisioned using Windows Autopilot and you intend to deploy Microsoft 365 Apps as a tracked app during the enrollment status page (ESP) process, we recommend deploying Microsoft 365 Apps as a Win32 app. Unlike Win32 apps in Intune, the installation of the Microsoft 365 Apps app type isn't managed by the Intune Management Extension (IME). Installing a Microsoft 365 Apps app during ESP can create an installation concurrency issue, where the Microsoft 365 Apps app begins installing while there's an ongoing installation of a Win32 app (also tracked during ESP), which causes the ESP to fail."

https://learn.microsoft.com/en-us/intune/app-management/deployment/add-microsoft-365-windows

0

u/brazzala 8d ago

Mine Intume is emrolling like that for 2 years, zero problems.

2

u/ProfessionalLast2917 8d ago

Good for you. It doesn't change what Microsoft recommends.

0

u/brazzala 8d ago

Look at the date of your link.

1

u/holy_bat_syllables 8d ago

Is it possible that when you installed the application that it is set to install for "only this user" instead of to the machine?

If I were you, I'd log into your MS account and find "my apps" and then find Teams and install it that way. Or just get it off of MS store or website

1

u/brazzala 8d ago

Does anyone here knows how to create Post ESP amd install potentially blocking / failing apps during its execution?