I am investigating why I cannot set up a hook to integrate Teams and Azure DevOps. I am running two versions in different environments for comparison- but I am trying to hook the two together in the same environment.
First environment, version 1.3.00: This has the app built-in for Azure DevOps to hook and connect with Teams
Second environment, version 1.2.00: This version has no 'manage apps' button, and does not have anything referencing Azure DevOps or allowing to make any connection between Azure and Teams. This is the environment I am trying to make the connection in.
Any thoughts on this? Does 1.2.00 version not offer the hook between Teams and Azure DevOps? We do not have O365 accounts for this environment.
To access the Manage apps page, you must be a global admin or Teams service admin. You may check your permission. Also, add microsoft-teams tag for you case may help you get more assistance.
https://learn.microsoft.com/en-us/microsoftteams/manage-apps
Related
i'm creating EMM-managed enterprise. This is the recommended method (no signup page nor google account required)
https://developers.google.com/android/management/create-enterprise#emm-managed_enterprises
but, with this enterprise, end user have no IT admin account to connect to managed google play on https://play.google.com/work
what is the correct way to approve applications with this type of enterprises?
EMM Managed enterprise is no longer the recommended method to create an enterprise, Instead, we suggest starting a Customer-managed enterprises.
Additionally, with Android Management API any application added under the application policy behaves based on the configured installType. The play store mode policy determines the behavior of the apps on the device play store.
You will still need to follow all of the policy distribution steps mentioned in this documentation.
I'm struggling with moving our VSTS subscription (and all projects within it) to a new MS work Azure account.
The original VSTS subscription was created on a personal account (call it a#a.com) and I want to move it to a#a.onmicrosoft.com.
When I am in the azure portal I can see the Team Service as a resource. I've unlinked it from any active directory.
Now, while it has a subscription key, I cannot seem to access the subscription. There is no link and there are zero subscriptions listed on the subscriptions list in Azure portal. it seems to be orphaned or something.
I have tried adding a#a.onmicrosoft.com as a user to the VSTS account within VSTS but it seems to add it as a personal account, so I cannot log in to it using my work account.
I have managed to change the owner in VSTS to a Gmail account, but it's still showing as a resource in my a#a.com personal Azure account.
I have tried to find up to date information on this but several pages mention adding a co administrator, but either this is no longer possible or I cannot do it because there appears to be no subscription association with the VSTS resource.
I'm desperate, please help!
In the end I had to raise a support ticket with VSTS support who performed some kind of migration that I would have been unable to do myself.
Looking for information on how to integrate VSTS to Office365: Outlook. Essentially looking for a method whereby a team member that does a great amount of fix-it tickets can drop them into the Azure DevOps Project from Outlook as many of those tickets get passed to her from users through email.
A right click >> add new task from Outlook to Azure DevOps would be ideal.
There is no built-in feature, but you can work miracles with Microsoft Flow, basically, the If This Then That from Microsoft. it comes with built-in tasks to trigger on Outlook/Office 365. Moving an email to a specific folder or tagging it with a specific tag would be enough for Flow to trigger a rule.
This template rule uses the "When an email is tagged" and this template rule creates a Bug work item based on a trigger. Combining these two should let you achieve what you're looking for.
If you want integration in the Outlook Windows client, then there are a couple of commercial options available: There are a couple of add-ins for Outlook. Team Companion, TeamLook and TFS Work Item from Outlook spring to mind.
An alternative option is to use an Azure Function which is triggered by Azure DevOps Service Hooks. Not sure if you can bind an Azure Function to an Office 365 mailbox. Flow could act as an intermediary here as well.
You might want to check this tool called TMO that will enable you to create and manage work items from Outlook. It also allows you to automatically create work items in Outlook using a rule based engine called Auto Pilot
I had the same issue and just downloaded the TMO tool, and it works great. It does what I expected, once I figured out how to find the URL to connect to my Azure Dev Ops (ADO) server. Note: ADO is the new name for TFS or VSTS.
There's also a PowerAutomate called Create an Azure DevOps work item when email arrives with 'Bug' in subject that does just what it says. If that doesn't work for you, try modifying this one or creating your own.
Linda
I'm looking at using the Bot Framework (https://docs.botframework.com) is it possible to register a bot programmatically e.g via service? I see there are Azure bots but still don't see a way to register via service?
At the moment you have to manually log into the portal to register the bot and obtain your keys. There has not been any indication from Microsoft that this will change in future.
from what I know about the goals of the dev team, since this is a highly requested feature, we will probably see this in action in future version of the bot framework.
But no kind of timeline yet for this feature.
I want to create a bot, but I am confused what is exactly Bot Framework and Azure Bot service? Can anyone explain in detail?
The best way to understand the difference is going through the docs. The Azure Bot Service documentation is available here.
In a nutshell, Azure Bot Service provides a set of templates to get started with the creation of Bots and accelerate the development since it provides an integrated environment. Of course, the templates that it creates are based on the BotFramework. With Azure Bot Service, you can even code your bot directly from the Azure Portal Editor, from the comfort of your browser.
If you don't want to start with Azure right way, and want to develop your Bot locally first, etc, you might want to use the BotFramework builder bits; but as I said; once you se Azure Bot Service, you are able to download the generated bot and continue the development from your machine if you want.
Admittedly you asked your question a year and a half ago, but in early 2018 it seems as though Microsoft uses the two terms interchangeably for one product.
Take, for example the documentation link from the bot framework home page, the title of this page is Bot Service Documentation:
https://learn.microsoft.com/en-us/bot-framework/
Also, in the Azure pricing calculator only Azure Bot Service is listed (under both "Analytics" and "AI + Machine Learning"). "Azure Bot Service" is what appears on the invoice.
Finally, when you go to create a new resource and search for "bot" the only related items that you will see are for Azure Bot Service, there is no mention of Azure Bot Framework there either.
Bot Framework - is comprised of an open-source SDK and tools for end-to-end bot development.
Azure Bot Services - a cloud platform that hosts bots, helps you manage, connect, and deploy your bot across devices and popular channels
Bot Framework Service - a component of Azure Bot Service, that responsible to sending the info between the app and the channel
Microsoft Bot Service SDK