Hello,

This is pushing me to the edges.

Whenever I send private messages I got below errors. I don’t even know what it means, and no idea on how to fix it.

I am using Google Chrome on Mac (if that is useful information).

I tried to send test message that contains only text to myself, no URLs, no attachment, no spelling errors, no special characters, still got this error.

And the most exciting thing about this: if I click the send button more than twice, I will be locked out of sending any private messages at all for at least one hour.

Can anyone help?????

​Hello, This is pushing me to the edges.Whenever I send private messages I got below errors. I don’t even know what it means, and no idea on how to fix it.I am using Google Chrome on Mac (if that is useful information).I tried to send test message that contains only text to myself, no URLs, no attachment, no spelling errors, no special characters, still got this error.And the most exciting thing about this: if I click the send button more than twice, I will be locked out of sending any private messages at all for at least one hour. Can anyone help?????  Read More

​

 Hello I’ve published my copilot studio on Teams.

Whenever I use the desktop computer, everything works fine.

When I use the mobile application, if I am not authenticated on MS Teams on the desktop, when a generative node is called, the app simply does not respond, without returning any error. As soon as I access the chat on the desktop computer, all pending responses are returned and synchronized in the mobile app. If I am authenticated on MS Teams on the desktop, the mobile application also works fine. I also tested this: when I use the mobile application, if I have an active authentication on MS Teams in the mobile browser with the desktop site enabled, the mobile application also works fine. I have also tested the following, but always with the same result of the mobile application not responding to generative nodes: – I tried different Wi-Fi networks and mobile data – I reinstalled the app on my phone – I cleared the cache in the mobile app – I tested on both Android and iOS – I tested with different users Any idea why the mobile application doesn’t work with generative nodes when I don’t have an active authentication on a desktop version?

​ Hello I’ve published my copilot studio on Teams. Whenever I use the desktop computer, everything works fine.When I use the mobile application, if I am not authenticated on MS Teams on the desktop, when a generative node is called, the app simply does not respond, without returning any error. As soon as I access the chat on the desktop computer, all pending responses are returned and synchronized in the mobile app. If I am authenticated on MS Teams on the desktop, the mobile application also works fine. I also tested this: when I use the mobile application, if I have an active authentication on MS Teams in the mobile browser with the desktop site enabled, the mobile application also works fine. I have also tested the following, but always with the same result of the mobile application not responding to generative nodes: – I tried different Wi-Fi networks and mobile data – I reinstalled the app on my phone – I cleared the cache in the mobile app – I tested on both Android and iOS – I tested with different users Any idea why the mobile application doesn’t work with generative nodes when I don’t have an active authentication on a desktop version?  Read More

​

MkDocs is a simple static site generator that’s geared towards building project documentation. Documentation source files are written in Markdown, and configured with a single YAML configuration file.

This tutorial will demonstrate how to host an Mkdocs project dynamically or statically. You can choose either method to publish your project based on your needs, and the two approaches are independent of each other.

TOC:

Dynamic Hosting in Development Environment
Static Hosting in Development Environment
Dynamic Method: Using Python Web App
Static Method: Using Node Web App

Static Method: Using Static Web App

References

Dynamic Hosting in Development Environment

STEP 1:

Use VSCode to open an empty folder. Start a terminal and input the following commands to create a Python virtual environment and switch the current session to this environment.

Windows

python -m venv .venv
..venvScriptsActivate.ps1

Linux

python -m venv .venv
source .venv/Scripts/activate

STEP 2:

Enter the following commands to create an Mkdocs project (for example, my-project), switch to the project directory, and start the project. You will then be able to visit the project page in your browser at http://127.0.0.1:8000.

pip install mkdocs
mkdocs new my-project
cd my-project
mkdocs serve

Static Hosting in Development Environment

STEP 1:

Once the project is created in the development environment, the pages originally displayed must be rendered using Python and the Mkdocs package. We can run the following commands to build these pages into pure static HTML, making them deployable to any static website hosting service, such as Azure Static Website or the Azure Web App introduced here.

After the project is built, you will find the corresponding static web pages in the newly created site subfolder. You can open index.html in your browser to see the project page.

mkdocs build

Dynamic Method: Using Python Web App

STEP 1:

Create a Linux Python Web App on Azure.

STEP 2:

Using VSCode, add two files, “mkdocs.sh” and “.deployment”, to the root directory of your project.

mkdocs.sh

pip install mkdocs
cd /home/site/wwwroot/my-project/
mkdocs serve -a 0.0.0.0:8000

.deployment

[config]
SCM_DO_BUILD_DURING_DEPLOYMENT=false

STEP 3:

Deploy the root directory of the project to the Python app you just created using VSCode.

STEP 4:

On Azure, find the Python app and modify the startup command as follows, then restart the app.

bash /home/site/wwwroot/mkdocs.sh

STEP 5:

Check if your project is running correctly.

Static Method: Using Node Web App

STEP 1:

Create a Linux Node Web App on Azure.

STEP 2:

In the Mkdocs subfolder of your project, find the site folder, and add a .deployment file inside it.

.deployment

[config]
SCM_DO_BUILD_DURING_DEPLOYMENT=false

STEP 3:

Deploy the “site” subdirectory of your project to the Node app you just created using VSCode.

STEP 4:

On Azure, find the Node app, modify the startup command, and restart the app.

pm2 serve /home/site/wwwroot –no-daemon

STEP 5:

Check if your project is running correctly.

Static Method: Using Static Web App

STEP 0:

You can create a GitHub repository for the entire project folder (for example, I’ve named it mkdocs-app), or you may choose to only upload the “site” subdirectory, depending on your needs. In this example, I’ll use the entire project folder.

STEP 1:

Create a Static Web App on Azure and specify your project’s GitHub repository and the corresponding branch during the process. Please note that you’ll also need to set your App Location/Output Location as follows, adjusting the name to your “mkdocs project” (for example, my-project).

./my-project/site

STEP 2:

Once the SWA is created, you can check the deployment status in the GitHub repository. After the deployment is complete, you’ll be able to see the actual page.

STEP 3:

Verify that your project is running properly.

References

MkDocs

Azure Linux Web App and http server – Microsoft Community Hub

Quickstart: Build your first static web app | Microsoft Learn

​Microsoft Tech Community – Latest Blogs –Read More 

Our customers require daily refreshes of their production database to the non-production environment. The database, approximately 600GB in size, has Transparent Data Encryption (TDE) enabled in production. Disabling TDE before performing a copy-only backup is not an option, as it would take hours to disable and re-enable. To meet customer needs, we use a customer-managed key stored in Key Vault. Azure Data Factory is then utilized to schedule and execute the end-to-end database restore process.

Permission requires

To perform backup and restore operations, the SQL Managed Instance Managed Identity needs to have the “Contributor, Storage Blob Data Contributor” permission for the blob storage.
To transfer backup files between two storage locations, ADF managed identity needs the “Storage Blob Data Contributor” permission for the blob storage.
To carry out backup and restore operations, ADF managed identity needs ‘sysadmin’ permissions on SQL Managed Instance.
To enable Transparent Data Encryption (TDE) with a customer-managed key, ensure you have Contributor access to the Resource Group (RG) where the SQL managed instance resides.
Establish an Azure Key vault access policy for the SQL managed instance’s managed identity and the user configuring Transparent Data Encryption (TDE), granting them full key permissions.

Step 1

Create a TDE key in the non-production Azure Key Vault dev-kv-001 within the same subscription as the non-production SQL Managed Instance.

Name the key, select RSA with a 2048-bit key size, and leave the active and expiration dates unset for this demonstration. Ensure the key is enabled, and do not set a rotation policy. Finally, click Create.

Step 2

Establish an Azure Key vault access policy for the SQL managed instance’s managed identity and the user configuring Transparent Data Encryption (TDE), granting them full key permissions.

Step 3

Backup the TDE key we just created with in non-prod key vault

Step 4

Create a new Key Vault dev-kv-002 and proceed to restore the key within this newly created vault. Ensure the name matches the backed-up key name and that the status is set to enabled.

Step 5

Move the new dev-kv-002 Azure Key Vault from the development (non-prod) subscription to the production subscription. This process may take a few minutes as it validates the ability to move the Key vault.

Step 6

Having successfully moved our Key Vault dev-kv-002 to the production subscription, we will now proceed to backup (Follow step 3) the Key for restoration in the actual production Key vault prod-kv-001

Step 7

We are now prepared to link the keys we created with their respective Azure SQL Managed Instances in both the development and production environments. The objective is to maintain the same key in the backup, enabling us to refresh our production environment into development seamlessly.

We will simultaneously execute these actions in both our Production and Development SQL Managed Instances. Begin by accessing your portal blades for the SQL Managed Instances. Once there, navigate to the SQL Managed Instance blade and select Transparent Data Encryption under the Security section.

To enable a successful production refresh of our development environment, we need to switch from Service-managed keys to Customer-managed keys.

Step: 8

Creates a server-level credential. A credential is a record that contains the authentication information that is required to connect to a resource outside SQL Server.

USE master
CREATE CREDENTIAL [https://<mystorageaccountname>.blob.core.windows.net/<mystorageaccountcontainername>]
WITH IDENTITY=’Managed Identity’
GO

Step: 9

Create ADF link service connects for both SQL Managed Instances and storage accounts.
Create ADF dataset using both SQL Managed Instances and storage accounts link services

Step: 10

If you’re utilizing a private endpoint, make sure to set up an ADF integration runtime and a managed link follow Create Azure Data Factory Managed Private Links

Step: 11

Create ADF pipeline to take database backup from source.

Split backup files into multiple files for faster backup
Use below scripts to take copy only database backup
Use Script activity to execute the backup scripts using source SQL MI link service

BACKUP DATABASE [@{pipeline().parameters.source_database_name}]
TO URL = N’https://<storageaccountname>.blob.core.windows.net/databaserefresh/@{pipeline().parameters.source_database_name}_01.bak’,
URL = N’https:// <storageaccountname>.blob.core.windows.net/databaserefresh/@{pipeline().parameters.source_database_name}_02.bak’,
URL = N’https:// <storageaccountname>.blob.core.windows.net/databaserefresh/@{pipeline().parameters.source_database_name}_03.bak’,
URL = N’https:// <storageaccountname>.blob.core.windows.net/databaserefresh/@{pipeline().parameters.source_database_name}_04.bak’,
URL = N’https:// <storageaccountname>.blob.core.windows.net/databaserefresh/@{pipeline().parameters.source_database_name}_05.bak’,
URL = N’https:// <storageaccountname>.blob.core.windows.net/databaserefresh/@{pipeline().parameters.source_database_name}_06.bak’,
URL = N’https:// <storageaccountname>.blob.core.windows.net/databaserefresh/@{pipeline().parameters.source_database_name}_07.bak’,
URL = N’https:// <storageaccountname>.blob.core.windows.net/databaserefresh/@{pipeline().parameters.source_database_name}_08.bak’
WITH COPY_ONLY, MAXTRANSFERSIZE = 4194304, COMPRESSION, STATS = 10

Allow a minute for the backup to transfer to blob storage, adjusting the duration to meet your specific needs.

Step: 12

Create ADF pipeline to copy database backup files from source storage account to target storage account.

Use copy activity to copy backup files from source storage account to target storage account.
Allow a minute for the backup to transfer to blob storage, adjusting the duration to meet your specific needs.

Step: 13

Create Azure Data Factory pipeline to restore database to a target SQL Managed Instance backup from the designated storage account.

Use below scripts to restore database from designated storage account
Use Script activity to execute the restore scripts using target SQL MI link service

USE [master]

RESTORE DATABASE [@{pipeline().parameters.target_database_name}] FROM
URL = N’https://<storageaccountname>.blob.core.windows.net/databaserefresh/@{pipeline().parameters.source_database_name}_01.bak’,
URL = N’https://<storageaccountname>.blob.core.windows.net/databaserefresh/@{pipeline().parameters.source_database_name}_02.bak’,
URL = N’https:// <storageaccountname>.blob.core.windows.net/databaserefresh/@{pipeline().parameters.source_database_name}_03.bak’,
URL = N’https:// <storageaccountname>.blob.core.windows.net/databaserefresh/@{pipeline().parameters.source_database_name}_04.bak’,
URL = N’https:// <storageaccountname>.blob.core.windows.net/databaserefresh/@{pipeline().parameters.source_database_name}_05.bak’,
URL = N’https:// <storageaccountname>.blob.core.windows.net/databaserefresh/@{pipeline().parameters.source_database_name}_06.bak’,
URL = N’https:// <storageaccountname>.blob.core.windows.net/databaserefresh/@{pipeline().parameters.source_database_name}_07.bak’,
URL = N’https:// <storageaccountname>.blob.core.windows.net/databaserefresh/@{pipeline().parameters.source_database_name}_08.bak’

Step: 14

Set up an additional pipeline to remove orphan databases users, provide user access, or carry out any extra tasks needed after a restore, using the suitable activity task.

Step: 15

Create ADF pipeline workstation to execute all Step4 > Step5>Step6>Step7 in sequence.

Set up parameters for both the source_database_name and target_database_name to enable dynamic operation of the pipeline across different databases.

​Microsoft Tech Community – Latest Blogs –Read More 

At one point my Windows 11 crashed and when I reopened it, the file explorer looked weird with all those spacing as drawn in the picture attached being enlarged. How do I return it to normal?

​At one point my Windows 11 crashed and when I reopened it, the file explorer looked weird with all those spacing as drawn in the picture attached being enlarged. How do I return it to normal?   Read More

​

If you encounter issues while restoring an Azure SQL Managed Instance database from Azure blob storage, ensure that your database backup files are correctly stored in Azure blob storage.

Error: 1

Cannot open backup device ‘https://mystorageaccount.blob.core.windows.net/test_container/db_backup/mytest_db_01.bak‘. Operating system error 86(The specified network password is not correct.).

RESTORE DATABASE is terminating abnormally.

Cause of failure

The blob storage credential is either incorrect or missing.

To validate credential

I am utilizing managed identity, but the same approach applies to all identity types. SQL managed instance managed identity Storage Contributor and Storage Blob Data Contributor is require.

select * from sys.credentials

To create credentials

USE master
GO
CREATE CREDENTIAL [https:// mystorageaccount.blob.core.windows.net/db_backup/]
WITH IDENTITY=’Managed Identity’
GO

Error: 2

Cannot open backup device ‘https://mystorageaccount.blob.core.windows.net/test_container/db_backup/mytest_db_01.bak‘. Operating system error 12007(failed to retrieve text for this error. Reason: 317).

RESTORE DATABASE is terminating abnormally.

Cause of failure

The storage account’s public network access is disabled, relying solely on a private endpoint. However, the private endpoint was either configured incorrectly or associated with the wrong DNS zone, leading to connectivity issues. The private endpoint for blob storage must be created with privatelink.blob.core.windows.net Private DNS zone.

To validate private endpoint DNS configuration

Navigate Storage account > Network > Private Endpoint > Click Private Endpoint > Setting > DNS configuration.

FQDN: mystorage.privatelink.blob.core.windows.net
Private DNS Zone: privatelink.blob.core.windows.net

​Microsoft Tech Community – Latest Blogs –Read More 

We’re thrilled to announce the upcoming Capability Envisioning AI webinar, Microsoft ISV AI Envisioning Day: Get the Framework to Develop AI Solutions, designed to empower ISVs (Independent Software Vendors) with the tools and frameworks needed to fast-track the creation of commercial – grade AI solutions.

What’s in store:

Framework Deep Dive: Understand the Capability Envisioning framework—a strategic approach to accelerate AI solution development.
Expert Insights: Learn from leading AI professionals at Microsoft who will share their experiences and best practices.
Interactive Q&A: Engage with our experts and get your AI queries answered in real-time.
Exclusive Resources: Access a wealth of materials to help you design and develop top-notch AI solutions.

This webinar is a unique opportunity to harness the potential of AI and transform your business processes. Whether you’re a seasoned pro or new to the AI scene, our Capability Envisioning framework offers valuable insights and practical guidance.

You can register now for Microsoft ISV AI Envisioning Day: Get the Framework to Develop AI Solutions.  The webinar will run monthly so use this link to check back for future dates.  You can check out the framework here and get ready to supercharge your AI journey.

Let’s pave the way for the future of AI—together! 

#CapabilityEnvisioning #AIInnovation #MicrosoftCloud #ISV #Webinar

Can’t wait to see you there!

​Microsoft Tech Community – Latest Blogs –Read More 

I’m trying to make an AdaptiveCard that will show some information about an outage. This JSON looks great on adaptivecards.io/designer, but everything inside the ‘body’ isn’t rendered in Teams.

Here is an image of what appears when I try to call the webhook.

And here’s what it looks like on adaptivecards.io

{
“text”: “Datto Alert Raise on [device_hostname] [device_description] | [site_name]”,
“fallbackText”: “Datto Alert Resolve on [device_hostname] [device_description] | [site_name]”,
“$schema”: “http://adaptivecards.io/schemas/adaptive-card.json”,
“type”: “AdaptiveCard”,
“version”: “1.5”,
“body”: [
{
“type”: “TextBlock”,
“size”: “default”,
“weight”: “default”,
“color”: “default”,
“text”: “Datto”
},
{
“type”: “TextBlock”,
“text”: “New Datto RMM alert”,
“wrap”: true
},
{
“type”: “TextBlock”,
“text”: “New alert on [device_hostname] [device_description] | [site_name]”,
“wrap”: true,
“size”: “Medium”,
“weight”: “Bolder”
},
{
“type”: “TextBlock”,
“text”: “IP address: [device_ip] | Last user: [lastuser]”,
“wrap”: true,
“color”: “Dark”
},
{
“type”: “FactSet”,
“facts”: [
{
“title”: “Category:”,
“value”: “[alert_category]”
},
{
“title”: “Description:”,
“value”: “[alert_message]”
}
]
}
],
“actions”: [
{
“type”: “Action.OpenUrl”,
“title”: “New UI View Device”,
“url”: “https://[platform]rmm.centrastage.net/device/[device_id]/[device_hostname]”
},
{
“type”: “Action.OpenUrl”,
“title”: “Old UI View Device”,
“url”: “https://zinfandel.centrastage.net/csm/device/summary/[device_id]”
},
{
“type”: “Action.OpenUrl”,
“title”: “New UI View Alert”,
“url”: “https://[platform]rmm.centrastage.net/alert/[alert_uid]”
},
{
“type”: “Action.OpenUrl”,
“title”: “New UI Web Remote”,
“url”: “https://[platform].centrastage.net/csm/remote/rto/[device_id]”
},
{
“type”: “Action.OpenUrl”,
“title”: “New UI View Site”,
“url”: “https://[platform]rmm.centrastage.net/site/[site_id]”
}
]
}

​I’m trying to make an AdaptiveCard that will show some information about an outage. This JSON looks great on adaptivecards.io/designer, but everything inside the ‘body’ isn’t rendered in Teams. Here is an image of what appears when I try to call the webhook. And here’s what it looks like on adaptivecards.io    {
“text”: “Datto Alert Raise on [device_hostname] [device_description] | [site_name]”,
“fallbackText”: “Datto Alert Resolve on [device_hostname] [device_description] | [site_name]”,
“$schema”: “http://adaptivecards.io/schemas/adaptive-card.json”,
“type”: “AdaptiveCard”,
“version”: “1.5”,
“body”: [
{
“type”: “TextBlock”,
“size”: “default”,
“weight”: “default”,
“color”: “default”,
“text”: “Datto”
},
{
“type”: “TextBlock”,
“text”: “New Datto RMM alert”,
“wrap”: true
},
{
“type”: “TextBlock”,
“text”: “New alert on [device_hostname] [device_description] | [site_name]”,
“wrap”: true,
“size”: “Medium”,
“weight”: “Bolder”
},
{
“type”: “TextBlock”,
“text”: “IP address: [device_ip] | Last user: [lastuser]”,
“wrap”: true,
“color”: “Dark”
},
{
“type”: “FactSet”,
“facts”: [
{
“title”: “Category:”,
“value”: “[alert_category]”
},
{
“title”: “Description:”,
“value”: “[alert_message]”
}
]
}
],
“actions”: [
{
“type”: “Action.OpenUrl”,
“title”: “New UI View Device”,
“url”: “https://[platform]rmm.centrastage.net/device/[device_id]/[device_hostname]”
},
{
“type”: “Action.OpenUrl”,
“title”: “Old UI View Device”,
“url”: “https://zinfandel.centrastage.net/csm/device/summary/[device_id]”
},
{
“type”: “Action.OpenUrl”,
“title”: “New UI View Alert”,
“url”: “https://[platform]rmm.centrastage.net/alert/[alert_uid]”
},
{
“type”: “Action.OpenUrl”,
“title”: “New UI Web Remote”,
“url”: “https://[platform].centrastage.net/csm/remote/rto/[device_id]”
},
{
“type”: “Action.OpenUrl”,
“title”: “New UI View Site”,
“url”: “https://[platform]rmm.centrastage.net/site/[site_id]”
}
]
}      Read More

​

Hello Insiders! We released 131.0.2889.0 to the Dev channel! This includes numerous fixes. For more details on the changes, check out the highlights below.

Microsoft Rewards: A million-dollar sweepstakes – Microsoft Bing Blogs

The next step in Bing generative search | Bing Search Blog

Added Features:

Help information has been added to some rows on the Profile Preference Page.
Introduced a new custom border for the save/update password flyout.

Improved Behavior:

Fixed an issue where browser would crash on startup after an upgrade installation on Android.
Fixed an issue when switching to any search engine would cause browser to crash on iOS.

Changed Behavior:

Resolved an issue where Sidebar apps were pre-installed for new users in Gamer Mode. 
Fixed an issue where the wallpaper was enlarged on the New Tab Page.
Resolved an issue where the New Tab and Edit icons in the tab group showed the same tooltip as the tab group name.
Fixed an issue where the media indicator was not displayed correctly after playing media in two windows and pausing one of them on YouTube.com or other sites.
Resolved an issue where the Top Sites were misaligned when switching to portrait mode and then returning to the New Tab Page while accessing feeds in landscape mode.
Fixed an issue where hovering over icon buttons in high contrast mode made the icons less visible in the Downloads section.
Resolved an issue where the Address bar’s fill color did not update to reflect theme changes.
Fixed an issue where the ‘Sort by’ and ‘View by’ groups under Favorites were incorrectly defined as Menu items.
iOS:

Resolved an issue where the text in the Soft-landing UI section appeared unclear under experimental settings on iOS.
Resolved an issue where the PDF toolbar would appear upon signing in with an AAD account on iOS.
Resolved an issue when, after clicking the ‘Exit InPrivate mode’ button, the New Tab Page would switch to dark mode on iOS.
Fixed an issue where the PDF toolbar would briefly appear on non-PDF pages on iOS.
Resolved an issue where ‘News and more’ would be displayed in feeds when the tab center was clicked while opening a new tab page on iOS.

See an issue that you think might be a bug? Remember to send that directly through the in-app feedback by heading to the … menu > Help and feedback > Send feedback and include diagnostics so the team can investigate.

Thanks again for sending us feedback and helping us improve our Insider builds.

~Gouri

​Hello Insiders! We released 131.0.2889.0 to the Dev channel! This includes numerous fixes. For more details on the changes, check out the highlights below.
Microsoft Rewards: A million-dollar sweepstakes – Microsoft Bing Blogs
The next step in Bing generative search | Bing Search Blog
 
Added Features:

Help information has been added to some rows on the Profile Preference Page.
Introduced a new custom border for the save/update password flyout.

Improved Behavior:

Fixed an issue where browser would crash on startup after an upgrade installation on Android.
Fixed an issue when switching to any search engine would cause browser to crash on iOS.

Changed Behavior:

Resolved an issue where Sidebar apps were pre-installed for new users in Gamer Mode. 
Fixed an issue where the wallpaper was enlarged on the New Tab Page.
Resolved an issue where the New Tab and Edit icons in the tab group showed the same tooltip as the tab group name.
Fixed an issue where the media indicator was not displayed correctly after playing media in two windows and pausing one of them on YouTube.com or other sites.
Resolved an issue where the Top Sites were misaligned when switching to portrait mode and then returning to the New Tab Page while accessing feeds in landscape mode.
Fixed an issue where hovering over icon buttons in high contrast mode made the icons less visible in the Downloads section.
Resolved an issue where the Address bar’s fill color did not update to reflect theme changes.
Fixed an issue where the ‘Sort by’ and ‘View by’ groups under Favorites were incorrectly defined as Menu items.
iOS:

Resolved an issue where the text in the Soft-landing UI section appeared unclear under experimental settings on iOS.
Resolved an issue where the PDF toolbar would appear upon signing in with an AAD account on iOS.
Resolved an issue when, after clicking the ‘Exit InPrivate mode’ button, the New Tab Page would switch to dark mode on iOS.
Fixed an issue where the PDF toolbar would briefly appear on non-PDF pages on iOS.
Resolved an issue where ‘News and more’ would be displayed in feeds when the tab center was clicked while opening a new tab page on iOS.

See an issue that you think might be a bug? Remember to send that directly through the in-app feedback by heading to the … menu > Help and feedback > Send feedback and include diagnostics so the team can investigate.
Thanks again for sending us feedback and helping us improve our Insider builds.~Gouri  Read More

​

There is no way to delete a billing profile or billing scope in Azure. Users can create a billing scope when setting up trial services but there is no way to purge these billing scopes. Why is this not possible?

​There is no way to delete a billing profile or billing scope in Azure. Users can create a billing scope when setting up trial services but there is no way to purge these billing scopes. Why is this not possible?  Read More

​