When I try to create a DevOps project In Azure portal
Home>DevOps Projects
When I click Add,ASP.NET Core, Web App Windows or Web App Linux
The only option for service plans is S1
The Pricing tier shows as S1 Standard
Is there any way to get a cheaper tier? Is there even a way to share the plan. There seems to be no choice on the create screen.
Yes, it is possible. Click the Change button to open Settings where you can change Pricing tier.
Related
Is there a way to deploy a Word Web add in via GPO on premise.
The user should see the add in directly in the start pane.
We have already set the trusted catalog via GPO for the manifest and it is working, but found so far no way to show the user add in automaticly
Thanks
GPO doesn't provide anything for that. You can read about possible ways in the Deploy and publish Office Add-ins article.
Feature requests on Tech Community are considered, when the dev team go through the planning process. Use the github label: “Type: product feature request” at https://aka.ms/M365dev-suggestions .
I am doing some research for Powerapps integration with Azure DevOps.
However there is limitated information for it.
It is possible to integrate powerapps inside a Task for AzureDevops?
Based on, that we have a .zip file with the Powerapp, and we want to create a Build and Release/Deploy for several environments.
Thank You.
It is possible to integrate powerapps inside a Task for AzureDevops?
Yes it is.
You can leverage the Solution concept of the Microsoft Power Platform and the Power Apps BuildTools (preview) extension for Azure DevOps.
Update 11/2020: This is now GA and called Power Platform Build Tools
I've written a complete step-by-step guide on this topic:
A Continuous Delivery Approach for No-Code Solutions in Microsoft’s Power Platform
Bottom line:
With this build tool, you can automatically check-in a Solution into source control and deploy it using a continuous delivery approach with the help of Azure DevOps. See the screenshot for a sample configuration of the Export and Import Solution Task.
It works for everything you can organize inside a Solution, e.g.:
Power Apps
Power Automate Flows
AI Builder Models
Common Data Service Entities
It is possible to integrate powerapps inside a Task for AzureDevops?
I am afraid there is no such Task integrate powerapps for AzureDevops at this moment.
If you want to integrate powerapps with azure devops, you can follow the guide step by step:
Microsoft Teams – Integration with Visual Studio Team Services using PowerApps.
Besides, AFAIK, PowerApps should not be "Build/Deployed" through Azure Devops.
When you are developing with PowerApps, there is no way to do Source
Control. There are no source files. The only artifact you can version
control is the .zip file that you can export.
And
In PowerApps, you don’t have to build your code. Any change you make
to the application is live for you to test it. In that way it is very
productive. To publish the application you just click on the publish
button and it is live.
Check this great blog: PowerApps From A DevOps Perspective for some more details.
Hope this helps.
Solutions are a way to package your components in a single zip file and use Powerapps build tools to import your solution on to a different environment or tenant.
It is still a an improvement from manually importing each app or environment variable and then import it on to target system, but it lacks what we call as automation of deployment.
To provide an eg, I will explain what I have done, and what still constitutes of a manual task:
I created an enterprise level app using powerapp canvas model. My app consumes data from around 20 APIs. These API calls are implemented in power automate.
We have 4 environments, dev, sit, uat and prod. Now I cant keep on importing flows in each environment and change their api URLs to point to the deployed environment. So I used environment variables for each environment which stores api URLs for each environment. This can be done under solution.
Under the same solution, I added my app. So now my solution has 2 things, my app and the environment variable which consists of api URLs.
I then use powerapps build tools to move this solution from dev to sit.
Steps: use build tools tasks to perform the following
Export solution
Unpack it in git
Pack it
Import the solution.
This successfully moves my solution to sit.
But the solution environment variable still points to the dev url.
So I have to override environment variables to store sit URLs.
This manual intervention to edit environment variable is as good as doing all the tasks manually.
This was the case when PowerApps was first announced; however, this is no longer the case.
While it is technically true that there is no actual code that would be managed and deployed with a PowerApp or Flow but that doesn't mean that you can not use the power of Azure DevOps. Additionally, when creating a PowerApp / flow you would also be creating entities and even Model Driven apps - and these uses solutions - which naturally work well to deplooy within Azure DevOps.
Microsoft is building out this whole construct to enable all these to deploy...
While the whole incorporation of PowerApps and flows into Solutions is not fully baked yet - they are targeting to have this ready around the October time frame this year.
We have been talking to Microsoft about also enabling PowerApps and flows to follow the same expansion that solutions do so that they can take advantage of the full branching strategy.
So even though you would be simply exporting out zip files into your repo - you can still take advantage of the full devops pipeline which is highly recommended.
Use this component, it still on preview mode but is working fine on my side
https://marketplace.visualstudio.com/items?itemName=microsoft-IsvExpTools.PowerApps-BuildTools
My project has two web apps (.NET) and 2 mobile apps (mobile apps built in Xamarin and deployed in iOS and Android).
Team is unclear on trade-offs between using Azure DevOps and MS AppCenter.
From this SO item
What's the principal difference between MS AppCenter and Azure DevOps (former VSTS)?
it seems that "...App Center is for mobile app deployment & monitoring whereas DevOps is for any-platform development & deployment."
But what are the trade offs between the two? I think we would like to do all builds in Azure DevOps and then feed these builds into App Center for deployment and monitoring, but is it possible to do this?
Any advice would be greatly appreciated.
App center is great if you want to quickly build and distribute mobile apps, it have build in tempate to deploy app to App Store , Google Play Store, Intune as well as analytics. However, the CI/CD is not very customisable.
Azure Devops is great for CI/CD customisable, you can configure the build, trigger build on pull request and etc... Also you can configure stages in CD. Also good for keeping your project, code and ci/cd in one place. However the deployment for mobile apps is not great, as there are no built in template at the moment, you can write your own yaml or get template from the market though.
Integration from Azure Devops and VS App Center give the best experience in my opinion.
I have been using azure PowerShell tasks to update my app settings in the portal for all the web apps and would like to know if there is any other way to do the same.
I don't want to make the changes in the config files alone. The changes have to be made in the azure portal as well.
There are a few third-party tools to accomplish this and avoid Powershell. Basically it takes your VSTS variables, and sets them in Azure. You install these as release tasks.
Azure WebApp Configuration task
Azure App Service: Set App settings
In current Azure stack you have two options.
For secured settings you should rather use "Azure Key Vault"
For Centralized app settings you should use "Azure App Configuration" which is in public preview.
I am running a mobile service with an increasing amount of scripted functionality. I want to have these scripts somehow stored in a smart format for version control. I'm having hard time finding any information on such scenarios. Is it even possible Azure -> VS2012 (and TFS) or VS2012 (and TFS) -> Azure?
Currently that is not supported on the portal itself. You can do that by using the Command Line Interface, however, as was shown in this blog post. Basically, you can store the scripts in whichever source control system you want (the post uses Git, but it would work with TFS as well) and use the CLI to update your service whenever a new version of the script is checked in.
You can also vote up the source control feature suggestion on the UserVoice for the system, to have that functionality implemented in the service itself.
You can now link your Azure Mobile scripts to a git repo directly from the Azure Mobile Portal Dashboard, allowing you to edit scripts from VS2012 or another editor.