by Contributed | Feb 18, 2021 | Technology
This article is contributed. See the original author and article here.
Today, we are sharing an update on the roll out status of the Windows 10 Team 2020 Update, following our previous update in January.
Throughout January, we listened to and worked closely with customers to resolve some of the issues reported on the known issues list, which will now be offered to customers updating to Windows 10 Team 2020.
Surface Hub 2S
Today, we are making the Windows 10 Team 2020 Update available for Germany and the Netherlands via Windows Update. The update will become available worldwide via Windows Update on February 23, 2021, completing the update offering for Surface Hub 2S devices anywhere on the planet.
The Windows 10 Team 2020 Update is also offered via Windows Update for Business, and we now offer an updated Bare Metal Recovery (BMR) image on the Surface Recovery Image webpage.
Surface Hub (first-generation)
We remain committed to starting Windows 10 Team 2020 Update rollout in late February as communicated in the previous update. More details will be provided closer to the release date.
Support for Microsoft Edge Legacy
Following the Microsoft Edge team’s announcement on Friday, February 5, 2021, about the end of support for Microsoft Edge Legacy on March 9, 2021, we encourage customers to install the new Microsoft Edge browser on all Surface Hub and Surface Hub 2S devices running the Windows 10 Team 2020 Update. The Microsoft Edge Legacy browser will remain the default browser on Surface Hubs until its replacement in a future update later this year.
As mentioned earlier, Windows 10 Team, version 1703 will remain supported through March 16, 2021. Please make sure to read the known issues list before updating your devices to Windows 10 Team 2020.
by Contributed | Feb 18, 2021 | Technology
This article is contributed. See the original author and article here.
I have been working on a support ticket were customer was getting the following error trying to save Auditing settings.
“Failed to save Auditing settings for server: xxx .Principal xxx does not exist in the directory xxx”.
During auditing configuration , customer had selected, an storage account that was being used by other Azure SQL server to save their auditing logs.
We confirmed that storage account was configured with firewall enabled
The problem came because, identity assignment was not getting saved correctly.
Executing the following query we could see that identity was not getting saved
select * from sys.database_scoped_credentials
The solution was reassign the Identity and resave auditing executing the following PowerShell command
Set-AzSqlServer -ResourceGroupName <NameofTheRG> -ServerName <NameOFTheServer> -AssignIdentity
If server also has TDE with AKV you will need to run :
$server = Get-AzSqlServer -ResourceGroupName rgname -ServerName server
$objectid = $server.Identity.PrincipalId
Set-AzKeyVaultAccessPolicy -VaultName vault -ObjectId $objectid -PermissionsToKeys get, wrapKey, unwrapKey
After apply mitigation, “select * from sys.database_scoped_credentials” output was the following, and auditing configuration could be saved correctly
Enjoy!
by Contributed | Feb 18, 2021 | Technology
This article is contributed. See the original author and article here.
The Azure Sphere OS update 21.02 is now available for evaluation in the Retail Eval feed. The retail evaluation period provides 14 days for backwards compatibility testing. During this time, please verify that your applications and devices operate properly with this release before it is deployed broadly via the Retail feed. The Retail feed will continue to deliver OS version 21.01 until we publish 21.02 in two weeks. For more information on retail evaluation see our blog post, The most important testing you’ll do: Azure Sphere Retail Evaluation.
The evaluation release includes an OS update only; it does not include an updated SDK.
Areas of special focus for compatibility testing with the 21.02 release should include:
- Apps and functionality utilizing /proc/<pid>/syscall.
- SNTP server functionality.
In addition, the 21.02 release includes updates to mitigate against the following CVEs:
- CVE-2021-3336
- CVE-2020-8285
- CVE-2020-8286
- CVE-2020-8284
- CVE-2020-8231
For more information on Azure Sphere OS feeds and setting up an evaluation device group, see Azure Sphere OS feeds and Set up devices for OS evaluation.
For self-help technical inquiries, please visit Microsoft Q&A or Stack Overflow. If you require technical support and have a support plan, please submit a support ticket in Microsoft Azure Support or work with your Microsoft Technical Account Manager. If you would like to purchase a support plan, please explore the Azure support plans.
by Contributed | Feb 18, 2021 | Technology
This article is contributed. See the original author and article here.
A Deep Dive into Serverless Applications on Power Apps and Azure
Overview
In 2021, each month we will be releasing a monthly blog covering the webinar of the month for the Low-code application development (LCAD) on Azure solution. LCAD on Azure is a new solution to demonstrate the robust development capabilities of integrating low-code Microsoft Power Apps and the Azure products you may be familiar with.
This month’s webinar is ‘A Deep Dive into Serverless Applications on Power Apps and Azure’ In this blog I will briefly recap Low-code application development on Azure, provide an overview of serverless, why to build a serverless Power App, and what to look forward to in the webinar’s demos.
What is Low-code application development on Azure?
Low-code application development (LCAD) on Azure was created to help developers build business applications faster with less code, leveraging the Power Platform, and more specifically Power Apps, yet helping them scale and extend their Power Apps with Azure services.
For example, a pro developer who works for a manufacturing company would need to build a line-of-business (LOB) application to help warehouse employees’ track incoming inventory. That application would take months to build, test, and deploy, however with Power Apps’ it can take hours to build, saving time and resources.
However, say the warehouse employees want the application to place procurement orders for additional inventory automatically when current inventory hits a determined low. In the past that would require another heavy lift by the development team to rework their previous application iteration. Due to the integration of Power Apps and Azure a professional developer can build an API in Visual Studio (VS) Code, publish it to their Azure portal, and export the API to Power Apps integrating it into their application as a custom connector. Afterwards, that same API is re-usable indefinitely in the Power Apps’ studio, for future use with other applications, saving the company and developers more time and resources.
Serverless Applications
You may be wondering what a serverless application is? Serverless is a cloud computing execution model where the cloud provider dynamically manages the allocation and provisioning of servers. A serverless application runs in stateless compute containers that are event-triggered, ephemeral, and fully managed by the cloud provider. In turn this model greatly benefits the developer and team by reducing their workload by reducing the need to manage servers, and this model is much cheaper because teams don’t incur the hardware and associated costs.
A logical next question is “in what scenario(s) do I go serverless?” You can choose it when you have asynchronous and concurrent tasks to be executed, when you have infrequent requests and spiky traffic where you don’t have a dependency on latency. Also, when you’re looking to quickly iterate your development, build MVPs, change your code or change business requirements to immediately deploy that code.
You’re now convinced of serverless code’s benefits, but how do you get started? At the core are cloud functions that enable you to write code in containers. In reaction to an event execution can be triggered by any of the managed services or any custom sources you might be defining that are important for your application. Due to durable functions you can write stateful functions in a serverless compute environment. Lastly, serverless code is event driven, running in response to specific triggers which can be a HTTP or a blob trigger when running code in response to a file being uploaded to a storage account number.
Serverless Power Apps
Building serverless applications on Azure sound great by themself, why would you bother to build your using Microsoft Power Apps? Building business applications quickly is not easy when utilizing several different frameworks, hosting options, and complex integrations between systems. Leveraging serverless technologies (Azure Functions and Logic Apps) can provide the building blocks for APIs to connect to custom backends, services, or a Data Model (Dataverse) that stores data across many applications. Leverage these APIs to deeply integrate with PowerApps or Power Automate and extend the data that is most critical to business users with apps that are quickly built, managed, and distributed. Moreover, with the development of ‘Fusion Development’ teams a term coined by analysts, developers can build back-end serverless APIs and import them via Azure API management directly into Microsoft Power Apps as custom connectors. ‘Citizen Developers’ or those who aren’t professional developers, can leverage these APIs in their Power App, reducing the overall work of the developer, by not having to build front-end code. Thus, piling on the time and resources saved by building serverless applications.
What to expect in the webinar?
Simona will cover first build a web API that generates jokes, throughout this process she will test and debug her APIs. Afterward publishing the API to which is available to test at aka.ms/joke which generates jokes using random words. Lastly, she exports the API to Power Apps via the Azure portal and challenges the viewers to extend her app with Power Automate AI chatbots that send jokes as text messages.
Summary
Make sure to tune into the webinar on February 25th to learn more about serverless APIs and how to export them into your Power Apps. Moreover, there will be a Low-code application development on Azure ‘Learn Live’ session during Ignite, the data loss prevention and new governance policies for Power Apps at Ignite, and an SAP on Azure Power Apps webinar in March.
Resources
Low Code Application Development on Azure
LCAD on Azure
Azure plus Power Apps for pro developers
Low Code Application Development on Azure – YouTube
Power Apps x Azure documentation
Azure integration document
Azure API Management integration announcement
Azure API Management integration documentation
Serverless documentation
Compare serverless options
Compare serverless options module
Azure Functions documentation
Azure Functions website
by Contributed | Feb 18, 2021 | Technology
This article is contributed. See the original author and article here.
A Deep Dive into Serverless Applications on Power Apps and Azure
Overview
In 2021, each month we will be releasing a monthly blog covering the webinar of the month for the Low-code application development (LCAD) on Azure solution. LCAD on Azure is a new solution to demonstrate the robust development capabilities of integrating low-code Microsoft Power Apps and the Azure products you may be familiar with.
This month’s webinar is ‘A Deep Dive into Serverless Applications on Power Apps and Azure’ In this blog I will briefly recap Low-code application development on Azure, provide an overview of serverless, why to build a serverless Power App, and what to look forward to in the webinar’s demos.
What is Low-code application development on Azure?
Low-code application development (LCAD) on Azure was created to help developers build business applications faster with less code, leveraging the Power Platform, and more specifically Power Apps, yet helping them scale and extend their Power Apps with Azure services.
For example, a pro developer who works for a manufacturing company would need to build a line-of-business (LOB) application to help warehouse employees’ track incoming inventory. That application would take months to build, test, and deploy, however with Power Apps’ it can take hours to build, saving time and resources.
However, say the warehouse employees want the application to place procurement orders for additional inventory automatically when current inventory hits a determined low. In the past that would require another heavy lift by the development team to rework their previous application iteration. Due to the integration of Power Apps and Azure a professional developer can build an API in Visual Studio (VS) Code, publish it to their Azure portal, and export the API to Power Apps integrating it into their application as a custom connector. Afterwards, that same API is re-usable indefinitely in the Power Apps’ studio, for future use with other applications, saving the company and developers more time and resources.
Serverless Applications
You may be wondering what a serverless application is? Serverless is a cloud computing execution model where the cloud provider dynamically manages the allocation and provisioning of servers. A serverless application runs in stateless compute containers that are event-triggered, ephemeral, and fully managed by the cloud provider. In turn this model greatly benefits the developer and team by reducing their workload by reducing the need to manage servers, and this model is much cheaper because teams don’t incur the hardware and associated costs.
A logical next question is “in what scenario(s) do I go serverless?” You can choose it when you have asynchronous and concurrent tasks to be executed, when you have infrequent requests and spiky traffic where you don’t have a dependency on latency. Also, when you’re looking to quickly iterate your development, build MVPs, change your code or change business requirements to immediately deploy that code.
You’re now convinced of serverless code’s benefits, but how do you get started? At the core are cloud functions that enable you to write code in containers. In reaction to an event execution can be triggered by any of the managed services or any custom sources you might be defining that are important for your application. Due to durable functions you can write stateful functions in a serverless compute environment. Lastly, serverless code is event driven, running in response to specific triggers which can be a HTTP or a blob trigger when running code in response to a file being uploaded to a storage account number.
Serverless Power Apps
Building serverless applications on Azure sound great by themself, why would you bother to build your using Microsoft Power Apps? Building business applications quickly is not easy when utilizing several different frameworks, hosting options, and complex integrations between systems. Leveraging serverless technologies (Azure Functions and Logic Apps) can provide the building blocks for APIs to connect to custom backends, services, or a Data Model (Dataverse) that stores data across many applications. Leverage these APIs to deeply integrate with PowerApps or Power Automate and extend the data that is most critical to business users with apps that are quickly built, managed, and distributed. Moreover, with the development of ‘Fusion Development’ teams a term coined by analysts, developers can build back-end serverless APIs and import them via Azure API management directly into Microsoft Power Apps as custom connectors. ‘Citizen Developers’ or those who aren’t professional developers, can leverage these APIs in their Power App, reducing the overall work of the developer, by not having to build front-end code. Thus, piling on the time and resources saved by building serverless applications.
What to expect in the webinar?
Simona will cover first build a web API that generates jokes, throughout this process she will test and debug her APIs. Afterward publishing the API to which is available to test at aka.ms/joke which generates jokes using random words. Lastly, she exports the API to Power Apps via the Azure portal and challenges the viewers to extend her app with Power Automate AI chatbots that send jokes as text messages.
Summary
Make sure to tune into the webinar on February 25th to learn more about serverless APIs and how to export them into your Power Apps. Moreover, there will be a Low-code application development on Azure ‘Learn Live’ session during Ignite, the data loss prevention and new governance policies for Power Apps at Ignite, and an SAP on Azure Power Apps webinar in March.
Resources
Low Code Application Development on Azure
LCAD on Azure
Azure plus Power Apps for pro developers
Low Code Application Development on Azure – YouTube
Power Apps x Azure documentation
Azure integration document
Azure API Management integration announcement
Azure API Management integration documentation
Serverless documentation
Compare serverless options
Compare serverless options module
Azure Functions documentation
Azure Functions website
Recent Comments