I'm developing a Microsoft Teams Tab App for internal company use. During development and testing, side-loading works good.
How do I distribute the app and make it available to all Teams and Channels in my tenant?
Unfortunately this is not yet supported, but we are working on it and hope to have it by early next year.
Related
I am trying to integrate A Chat Bot Service with A client who uses the Skype For Business Server 2019. On Microsoft Docs Page, I found that UCWA 2.0 exposes SFB Server 2015 instant messaging (IM) and presence capabilities. Could anyone please confirm whether this holds good for SFB Server 2019?
Do we have any better way to integrate the Bots with SFB Server 2019 other than UCWA 2.0 (As I came across the docs that mentioned UCWA having IM limitations and scaling issues)?
From this doc, Bot Framework also deprecated the support for Skype or business channel.
Please provide any information you have regarding this. Thanks in advance.
I suspect that UCWA will scale just fine, I know of some projects for pretty large organisations that have used it.
As an alternative you could look at UCMA 6.0 (which is more feature complete than UCWA), this is the SFB 2019 release and whilst I haven't seen any explicit documentation for this version I very much doubt it has changed much since UCMA 5.0 as the Microsoft strategy at the time of release was focused on Teams.
There’s 3rd party software available that can help with this, check out MindLink. Their API supports various versions of SfB server and I believe 2019 is covered too. You can apply throttling and other management capabilities so it is built to scale - it could be more for the enterprise, then again I don’t know what your project is.
I'm using visual studio 2019 for creating a bot application and I have run it successfully that I added the Bot in Microsoft Team using botframework.com and I was downloaded the MSTeam application and installed but it doesn't show my Bot app in msTeam Application
MSTeam channel creation in botframework:
MSTeam Application:
I have only 3 option such as activity, chats, calendar on the left panel
You Need to get access from admin account for app store to Microsoft teams.
In Office 365 admin center, in settings for Microsoft Teams. Turn on the option "Allow external apps in Microsoft Teams". So that you can view app studio in your Teams.
I don't have experience with botframework.com, but I'm assuming the behavior is going to be the same as when I manage bots through Azure. Turning on the channel itself isn't sufficient to add the bot to teams. There are (at least) two methods you can use to add the bot:
Copy the bot's Microsoft App Id and enter it into the To: field of a Teams chat. The bot should come up and you should be able to chat with it if the channel was set up correctly. It is not a good idea to share this app ID with others. I'd use this only for your own personal testing.
Create a Teams app manifest and load the app into Teams. There are a number of ways to create a manifest, but the easiest is to use the "App Studio" app from the Teams app store.
If you go the Teams app route, you can either sideload the app (which again, Teams App Studio makes that process easy but you can also Upload a custom app from the app store tab) or you can submit to your company app store. If you do not have a company app store, you'll need to sideload until you are ready to submit to the Microsoft App Store (if that is your end goal).
I need to create an administrative portal that is visually consistent with Office 365 and Exchange online / 2016
What UX experience is most similar to the admin portal in these situations?
I discovered Office Fabric but not sure what else is needed to get an Exchange administrator page.
Office UI Fabric team member here. I'm not sure if Fabric is currently used in the Exchange Admin Portal (I don't think so today), but as Slava points out, Fabric is the framework we use to build many of the apps & experiences throughout Office 365, with many pages and experiences being onboarded all the time. It's your best bet if you want to build a new UX that looks and feels like Office, specifically the Fabric-React components, since we stress-test these in our own products and hold them to a very high standard in terms of performance, accessibility, and feature set.
Yes, your research is correct. Office UI Fabric is the front-end framework for building experiences that fit seamlessly into Office and Office 365. Mainly the product made to be replicate Office applications (Word, Outlook, etc.) in 3rd party apps and add-ins. It should be suitable for administrative portal as well, but probably not that reach.
Office UI fabric has two mayor parts: One is Office UI Fabric Core which includes set of style sheets and the second Office UI Fabric JS which delivers built-in components you may use out of box with the core styles.
I am following a series of instructions to deploy a mobile backend using Azure Mobile Services.
As part of that workflow I get to download a personalized backend app which downloads as Visual studio solution.
It builds fine and the next step is to publish it to Azure.
Instead of seeing the choice below (Microsoft Azure App Service) I am seeing 2 different choices
Microsoft Azure Web Apps, or
Microsoft Azure API Apps (Preview).
So, I chose the closest option (Web Apps) provided and it logs me into Azure and in a box which reports existing web apps I see none.
Yet I've deployed a mobile app in the Azure portal earlier.
In some of what I've been reading online it mentions a Publisher profile. I am just a bit stumped by not getting the "Microsoft Azure App Service" choice when I go to publish my backend to the cloud.
Here is the tutorial/guide which I am following (January 2016).
Perhaps the VS/Azure integration has changed since then or maybe I've more configuration steps missing.
Azure .NET mobile backend using Azure Mobile Services
Any guidance would be hugely welcome.
At this stage I am stuck as far as what I need to do to get my mobile backend published to Azure.
You have got an older version of the Azure SDK installed. The latest version of the Azure SDK provides the Azure App Service publish dialog.
I think I've solved this for now.
I was able to download a publish profile from the Azure Console which I could import within the "publish" dialog in VS2015.
I now have the mobile app up and running in Azure.
Hi i'm new in creating windows phone app, can you tell me how can i install my app in my mobile with windows phone 7 ?
Currently the only way is to join the developer program for an annual subscription cost of USD $99. The ChevronWP7 team are supposedly working on releasing an official USD $9 unlock for homebrewers, but there's no word on when that will be available.
Installing the tools will allow you to run the application on the emulator to test it, but the afore mentioned membership is required to test on your phone or publish on the marketplace.
Deploy it using the Application Deployment program, or from within Visual Studio. You need to be a registered developer to do this. It costs $99 / year.
(I guess you aren't, since you otherwise wouldn't be asking)