I have developed an ASP.NET MVC5 app for Office365 using latest update of the Office 365 API Tools for Visual Studio. The app works fine with my own development Office365 site.
I understand that Visual Studio has registered the app in my Active Directory for me.
What I don't understand is how I am supposed to allow my customers to use this app with theirs Office 365 installations.
Somehow they are supposed to register the app in their Active Directory - that is the step I don't know how to explain to them.
Is there an automated way to provision the app registration to a customer's Active Directory?
The same way Visual Studio did it when I started the development? How did it do that? Through what kind of API?
You need to set your app in Azure AD to be multi-tenant. You can do this through the Azure Management portal. (Applications > [Your Directory] > Applications > [Your Application] > Configure).
Once the app is multi-tenant, your customer can navigate to the app and log in to trigger the common consent flow. Assuming that your customer has the permissions necessary to consent and allows the app to access their data, the customer will then be able to use the app with their Office 365 subscription.
Related
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).
This question is regarding the microsoft team app.
When i try to run the app created by other developers using visual studio microsfot team tool kit,
i get following error.
The app configuration in App Studio does not exist for the id 4f2c0a7d-6ab9-4594-b2b6-bec7ccd7d0e6 in the organization you are currently logged into.
I have logged into the teams and also uploaded the app package and allowed it for all teams.
Interestingly the app id in the admins.teams.microsoft.com is always different then the one in the client.
Regards
Ashish
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.
I have an existing Web API project published as a 'API App' on Azure. I recently added a "staging" deployment slot that I'd like to publish future versions of the API App before Swapping over to production. However, if I try to create a new publish profile in VS 2015 (or 2017), all my Web Apps are listed except the API App - so there is no way to select the existing deployment. Put this another way, if I delete the publish profile I have no way to publish the project using the Publish wizard (unless I download the publish profile from Azure, but I still have no way to change the deployment slot - that I know of).
I can see my API App in Cloud Explorer OK.
Any ideas?
I think you should be able to go to "deployment slots" in your web app click on a staging slot and then on the right side you will have your staging blade and then ou can download publish profile that is specific to staging slot:
According to your first screenshot, we could find that there are multiple resource groups in current subscription, but you just check the API App in resource group InergySystemsMain, please make sure if the API App belongs to other resource group.
Besides, as RAS said, we could download publish profile of Azure app service from Azure portal to local, and then we could import this publish profile file in Visual Studio.
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.