Microsoft 365 Community Community Demos, 18 May 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Introduction to Microsoft Teams Developer Portal

Description

In this 12-minute developer-focused demo, Karthig Balendran introduces viewers to the new and improved app management experience for developers. Access this tools portal from a browser and from within the Microsoft Teams client. This is the place to add (register and configure) your Teams apps. New safeguards to prevent any two apps from having same app IDs. Key areas differentiating the portal from App Studio are called out including that you can access App Source directly from this portal. This PnP Community demo is taken from the Microsoft Teams community call – May 2021, recorded on May 18, 2021

Demo Presenter: Karthig Balendran (Microsoft) | @KarthigBalendr1

Supporting documents:
• Site – Developer Portal for Microsoft Teams | http://dev.teams.microsoft.com/home

Learn more:
• Learn more about the Microsoft 365 Patterns and Practices community at: http://aka.ms/m365pnp
• Visit the Microsoft 365 Patterns and Practices community YouTube channel: https://aka.ms/m365pnp-videos

A

Hey everyone and welcome to uh my session. So this is the developer portal for microsoft teams. uh In a very, very quick nutshell, this is our new and improved app studio. Experience.

A

We've made it a website so that you can access it from the browser, and we will also be embedding it in teams just like app studio, so it should be accessible in the way that you're using it today, if you like, using app studio in the teams client, but we felt like we were missing an opportunity to really capture some value with app studio by really repurposing it as the app management console for developers.

A

Even if you look at the url here, it's dev.teams.microsoft.com, it's very similar to admin.teams.microsoft.com admins, have a portal where they can go and take administrative actions on the apps in the organizations that they've published or are waiting to publish the analysis of analytics on those apps how they're performing uh developers. You also need the same set of tools.

A

um Primarily app studio was used as a manifest editing experience and that's still there, but uh I we believe that there is more that can be done and we've set dev portal up as the foundation from which to build up this experience. So let me just get started with the bread and butter of the developer portal, and that is registering configuring.

A

Your team's app. I already have one right now. This is my list of apps already in my demo tenant, and I already have one app that I've created and adding a new app is as simple as adding one in app studio, you're just going to add an app. You get a name.

A

The one key difference between this experience and the one you get in app studio now is that we're going to be actually providing you with the unique app id for your teams app and that's going to be locked for this for the app registration that you provide. So you won't be able to go ahead and just provide your own good as the id for an app any longer.

A

So we're doing this because it's just enables us to provide some, more goodness in the developer portal, uh which I'll get you'll see in a second but also uh prevents collisions. uh We are running into errors by having people provide their own ideas where, in the back end, we were just observing that there were multiple apps of the same id and it was really difficult to consolidate that and figure out. What's the true representation of that app. So this should simplify things.

A

You are still going to be able to import an app from an app package if we detect that that app id has already registered to another app or belongs to an app, there will be a process to upgrade that this will not affect anything you already have in production. So rest assured that that this is just for pre-published apps. So this will not impact anything that you have in production out in the wild.

A

Already, I'm going to click into this app now and just see what the new configuration experience looks like we're, not boiling the ocean here, it's! uh It should be familiar to you. If you are familiar with editing your manifest in app studio, I'm going to go over the key areas that differ from app studio and the first one will be this owners page, and this will allow you to add contributors or administrators to an app let's say vasa and I are working on an app together at microsoft.

A

I don't want to email him. The zip package have him imported into app studio and start making changes. uh Much simpler approach would just be to add him as an owner or contributor. This you'll be seeing bugs as they head towards bill. This should be or not operative, which sounds a little bit evil, but you can idea is you can have an administrator who has full rewrite privileges to an app?

A

They can delete the app, and then you have contributors who can just change the configuration of an app next up is uh environment configuration, so you build an app you have it running on localhost, and then you push it to staging the content's being hosted somewhere like dev.azurewebsites.com and then finally, once it's ready to deploy up to production, it's being hosted in your production server.

A

Obviously your content, url endpoints, are changing and what we heard was people were just managing or had different, manifest files that represented each stage of their development pipeline and to simplify this uh we've. Provided this environment configuration feature in the dev portal, so I'm already created some variables here, but let me just walk through what it means, so you can go ahead and create an environment. I've created two environments, already carthage's local environment, car things, development, environment, and once you create an environment, you can start creating variables for that environment.

A

So here we have content url for local and it's pointing to localhost. And if I switch to my development environment, it's pointing to a random staging website and obviously the next step would be to create your production environment.

A

And then we also have a notion of global variables and let me go and show you how you would use these okay. So I'm going to go into capabilities, and here I've already created a personal app which at one point was called tabs and the content url right now. It's my local environment and it's pointing to locals 3000, but rather than hard code. This, let me go ahead.

B

A

A

Back here, okay, I'm not sure what happened. There's a bit of a bug. That's preventing me from editing this right now, let's do something else, I'm going to create a brand new one.

A

All right, I'm going to add a group one and I'm just going to say, content url rather than a hard-coded url value, and I'm going to say that this is for the channel scope and I'm going to save it.

A

And if you go to the manifest now, what you should see is rather than the environment variable name. You should see what that is pointing to so configurable tab perfect, so we actually did not enter a localhost 3000 tab. We entered content url, but it got injected into my local environment. Now. What we should do is go back here and do the exact same thing for the development environment so that okay, perfect okay, that's already taken care of, and I believe, we've already defined a content url for the development environment, perfect.

A

So let's go back the development environments, content url variable is set to dev.azure.com. So if we go back to the manifest and switch to dev, that's what we should see perfect excellent.

A

So we've made it a little bit easier for you guys to hopefully collaborate together with developers within your organization, we're exploring whether we want to extend this so that you can collaborate on apps with developers in other tenants. That's just something we're exploring right now, but right now, access to these apps is restricted to other members of your organization. You can't invite anyone outside of your organization, so that's something actually I'd be interested in hearing about from this community.

A

Are you interested in adding owners contributors, some other resource access group as a participant in an app in your tenant? For example, are you a service integrator working with clients and you'd like to invite some of your clients, development developers to share a particular app? So that's something we're interested in hearing about.

A

So let me step back here for a second and just take a look at this apps view right now so, like I said, this is restricted to apps in your organization and as a user, you only have access to the apps that you've registered yourself with the service or that someone has shared with you. One thing to note is that we will be exposing everything that you see.

A

In this view the all apps view and the per app view and the configuration capabilities that go into it in microsoft, graph, meaning there's going to be a microsoft graph api that says, get me app id this app id and then update basic information, short name to myapp2 or whatever.

A

So if you don't want to come to the developer portal, if you don't want to use this ui to configure your app registration or even create your app registrations, you can do so from the command line and just plug all of this into your ci cd pipeline.

A

In fact, there is going to be- uh let's go back here once more. Second, so right now, this is your all apps you. How do you add apps to this view? You can do it from the new app button. You can do it from the import app button. You can do it from microsoft, graph and microsoft.

A

Graph's entry point is also how our big toolkit 2.0 update, that will be coming out at build, we'll be registering apps with the team's app service.

A

So our goal is to accommodate how you work and make sure that you guys are effective and successful in your day-to-day jobs. So we do have some tooling that I don't want to spend too much time on right now, because I think these sort of speak for themselves and have used them in the past. You should be familiar with it. I would just like to open up the floor in case. There are questions coming in the chat. I will answer them now.

A

If anybody wants to unmute and ask me a question, I'm happy to take questions right now, too.

B

Thanks carter, so there was a cushion it's just commenting and having kept the capability of adding an external work to add, admins and dips would be really useful. So there's a one thumbs up on that one anybody else we would love to actually.

A

Can I dig into that actually absolutely so the person who asked the question so they said that that would be helpful. Would you mind just describing uh your scenario to me so that I understand it? Are you a service integrator? Are you somebody who uses consults consultants in your organization?

A

I would just love to learn more about that.

B

So we are, the meeting settings are unfortunately in a way that attendees cannot unleash uh so because we're having so many people on the on the meeting, but if cushion can actually elaborate on that one in the chat that would be really really good, then hilton is commenting.

B

uh Presumably this would be a part of viva connections deployment, so we could be actually integrating, and this one part of the vmware connections and vivo connections obviously is technically a microsoft teams application and that there will be a deep linking on that one to personal applications and bots as well. So there is a connection absolutely on that. So no changes from that perspective.

A

Okay, folks, uh if there are no other questions, what I will say is I will be presenting at build next week, so my session is vrk215, we'll be going over. Our pretty significant update to the team's toolkit, where we're going to be announcing awesome cool features like a new sdk, that's going to deliver single line, authentication and as well as you'll, see how the new toolkit will play nicely with the developer portal.

A

So stay tuned for that and before you go, I would like to show you one more nifty feature that we've added- and this is one of the reasons we had to lock down the id and it's so that we can provide this useful tile to you. So if you have an app registered in the app studio service and it's published to the team's app store, you're going to actually be able to see, I haven't published this.

A

Yet this is just the demo hack, but uh what you will see is actually friend charts that will track uh active users for your app over a period of seven days, 30 days and 60 days, okay and we're still figuring out what that looks. Like for the lob space, if you're building line of business applications so I'll leave you with that.

B

That's actually really really cool feature and so widely asked for appsource as well, so really really cool to have it and directly in the developer portal. But thank you kartik on that one and and like already promoted so many times in microsoft, built there's an awesome set of sessions and awesome announcements coming up on the team's platform. Don't miss them out! Kartik is going to do a live session there as well. Unless I'm completely mistaken, it is a live session. Isn't it.

A

B

Yeah there we go so, and so that's going to be really really cool and awesome set of features coming out on the team's toolkit v2 as well, but let's not talk about those yet because somebody would be angry. Who would do that? Thank you. Thank you.

A