On premise azure devops and microsoft teams - microsoft-teams

Is it possible to integrate an on premise instance of azure devops with Microsoft teams? I've seen there are the azure pipelines and other such apps, which look to do exactly what we want, but they only seem configurable with azure devops Services (cloud based). Also I've seen references to a Microsoft teams integration app, but that no longer seems to exist. Any help / advice would be much appreciated.

Check Azure DevOps Server, it will be used to do integration with on premise azure devops.

Related

Can we use Azure DevOps Pipelines to disable some Dynamics 365 custom plugins following deployment?

We are using Azure DevOps Pipelines with the https://github.com/WaelHamze/dyn365-ce-vsts-tasks extension to deploy our managed solution to Dynamics 365 online. We enable all plugin steps on deployment. Following deployment, we have a requirement to disable a handful of plugin steps. Currently we do this manually. Anyone aware of how we can automate this in the DevOps Pipeline?
Did you already tried it with the "MSCRM Plugin Registration" Task? It is in beta right now but as far as I understood it you can "reset" an assembly and just don't register your steps you want to remove?

How can a team download server code from a Mobile App service on Azure Portal

We have a mobile app service on Azure Portal.
We are a team with 3 members.
We hope to contribute to the server code (C#) together.
How can other teammates download the code which is published by one of us?
We could get the published files from azure WebApp with Azure kudu tool(https://www.sitename.scm.azurewebsites.net/), but the files are compiled, not the source code.
In your case, your team members could push your code to source control server such as github, VSTS,etc. Then team members could work together. And Azure WebApp(Mobile App) Allows us to continuous Deployment to Azure App Service. We could config Deployment options in azure portal.
In your app's menu blade in the Azure portal, click APP DEPLOYMENT > Deployment options. Click Choose Source, then select the deployment source.

Azure contributor access from Visual Studio

As security best practice our Client has restricted developer roles to Contributor on their Azure Portal resource group. All is fine but this seriously restricts using any kind of azure integration (deployments, server explorer, cloud explorer etc) from Visual Studio if we use the Contributor role to sign in to azure from Visual Studio. We are working on typical MSBI services like data lake analytics (usql), azure Analysis services, dw. And we cannot use any of the visual studio azure connectivity features.
I found a solution, to use a management cert. But MS site warns against using this as it will allow access to all azure resources defeating the purpose of contributor restrictions.
Could I please request for any guidance?
You can use RBAC'd accounts with VS, only the "legacy" features will not recognize them - e.g. Cloud Service Publish, Server Explorer (for this use Cloud Explorer instead).
Anything recent (AzureRM Tools, Cloud Explorer, Web Tools, Connected Svcs, Team Explorer) will work with RBAC
What features are you having trouble with?

How does one associate Visual Studio subscriptions with a company Azure subscription?

I have a Visual Studio subscription.
I'm trying to implement Application Insights in a Web API application in Visual Studio.
The wizard is trying to associate AI with my Visual Studio subscription. Rather, I want to integrate with my company's Azure subscription.
So, how is this done? Do I have to contact the Azure admin and add me to Azure? I have seen responses like "add you as a co-administrator". This is pretty dumb, when you're a developer.
Our company Azure subscription has Active Directory integration. So what. How do I register with the company Azure subscription that I want to implement services as a developer in the company??
Can someone provide some insight or references? The documentation is ponderous on this point.
If I understand your question correctly, you need to obtain an Instrumentation Key from a resource that is created in your company's Azure portal. Then, you can install application insights in your project and use that instrumentation key.
If, on the other hand you are asking why you have to be a co-administrator then you are correct. This was the case for a while but not anymore.
Account admin can now assign new users to specific resource groups. Each resource group can contain one or multiple resources. Read more: https://learn.microsoft.com/en-us/azure/active-directory/role-based-access-control-configure

Unexpected options when attempting to publish mobile service to Azure using VS2015

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.

Resources