You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/app-testing/load-testing/quickstart-create-run-load-tests-from-recording.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,13 +12,13 @@ ms.date: 12/16/2025
12
12
13
13
# Quickstart: Create and run a load test from a recording using AI
14
14
15
-
Learn how to use the Azure App Testing browser extension for Microsoft Edge to easily create JMeter load tests. The experience uses AI to enhance your test scripts by suggesting correlations, parameterizations, and other improvements. You can then run the load test at scale in **Azure Load Testing**.
15
+
Learn how to use the Azure App Testing browser extension for Microsoft Edge or Google Chrome to easily create JMeter load tests. The experience uses AI to enhance your test scripts by suggesting correlations, parameterizations, and other improvements. You can then run the load test at scale in **Azure Load Testing**.
16
16
17
17
This quickstart guides you through the steps of installing the browser extension, recording a user journey, reviewing and enhancing the generated load test script with AI assistance, and finally running the load test in **Azure Load Testing**.
18
18
19
19
## Prerequisites
20
20
21
-
- Azure App Testing browser extension for Microsoft Edge. [Download and install it here](https://aka.ms/AppTesting/Browser-Ext).
21
+
- Azure App Testing browser extension for [Microsoft Edge](https://aka.ms/AppTesting/Browser-Ext) or [Google Chrome](https://aka.ms/AppTesting/Browser-Ext-Chrome).
22
22
- An Azure account with an active subscription. Needed to run load tests at scale in **Azure Load Testing**. [Create an account for free](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn).
Copy file name to clipboardExpand all lines: articles/backup/backup-overview.md
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: What is Azure Backup?
3
3
description: Provides an overview of the Azure Backup service, and how it contributes to your business continuity and disaster recovery (BCDR) strategy.
4
4
ms.topic: overview
5
-
ms.date: 11/10/2025
5
+
ms.date: 01/23/2026
6
6
ms.custom: mvc, engagement-fy24, ignite-2024
7
7
author: AbhishekMallick-MS
8
8
ms.author: v-mallicka
@@ -19,15 +19,17 @@ The Azure Backup service provides simple, secure, and cost-effective solutions t
19
19
-**On-premises** - Back up files, folders, system state using the [Microsoft Azure Recovery Services (MARS) agent](backup-support-matrix-mars-agent.md), or use the DPM or Azure Backup Server (MABS) agent to protect on-premises VMs ([Hyper-V](back-up-hyper-v-virtual-machines-mabs.md) and [VMware](backup-azure-backup-server-vmware.md)) and other [on-premises workloads](backup-mabs-protection-matrix.md).
20
20
-**Azure VMs** - [Back up entire Windows/Linux VMs](backup-azure-vms-introduction.md) (using backup extensions), or back up files, folders, and system state using the [MARS agent](backup-azure-about-mars.md).
21
21
-**Azure Managed Disks** - [Back up Azure Managed Disks](backup-managed-disks.md)
22
-
-**Azure Files shares** - [Back up Azure File shares to a storage account](backup-afs.md)
22
+
-**Azure Files** - [Back up Azure Files to a storage account](backup-afs.md)
23
23
-**SQL Server in Azure VMs** - [Back up SQL Server databases running on Azure VMs](backup-azure-sql-database.md)
24
24
-**SAP HANA databases in Azure VMs** - [Backup SAP HANA databases running on Azure VMs](backup-azure-sap-hana-database.md)
25
25
-**Azure Database for PostgreSQL servers** - [Back up Azure PostgreSQL databases and retain the backups for up to 10 years](backup-azure-database-postgresql.md)
26
26
-**Azure Blobs** - Overview of [operational](blob-backup-overview.md?tabs=operational-backup)/ [vaulted](blob-backup-overview.md?tabs=vaulted-backup) backup for Azure Blobs
27
27
-**Azure Database for PostgreSQL Flexible server** - [Overview of Azure Database for PostgreSQL Flexible server backup](backup-azure-database-postgresql-flex-overview.md)
28
28
-**Azure Kubernetes service** - [Overview of AKS backup](azure-kubernetes-service-backup-overview.md)
29
-
-**Azure Database for MySQL - Flexible Server backup (preview)** - [Overview of Azure Database for MySQL - Flexible Server (preview)](backup-azure-mysql-flexible-server-about.md)
30
-
-**SAP ASE (Sybase) database backup on Azure VMs (preview)** - [About SAP ASE (Sybase) database backup on Azure VMs (preview)](sap-ase-database-about.md)
29
+
-**Azure Database for MySQL - Flexible Server** - [Overview of Azure Database for MySQL - Flexible Server (preview)](backup-azure-mysql-flexible-server-about.md)
30
+
-**SAP ASE (Sybase) database on Azure VMs** - [About SAP ASE (Sybase) database backup on Azure VMs](sap-ase-database-about.md)
31
+
-**Azure Data Lake Storage** - [About Azure Data Lake Storage vaulted backup](azure-data-lake-storage-backup-overview.md)
32
+
-**Azure Elastic SAN** - [About Azure Elastic SAN backup (preview)](azure-elastic-san-backup-overview.md)
> The functionality that the following sections describe can also be accessed via [Resiliency](../resiliency/resiliency-overview.md). Resiliency in Azure is a cloud-native unified experience for resiliency posture management that enables you to manage your protection estate across solutions and environments.
288
289
289
290
When you use the Azure portal, you can view the included and excluded disks from the VM backup details pane and the backup **Job Details** pane. During restore, when you select the recovery point from which to restore, you can view the backed-up disks in that recovery point.
Copy file name to clipboardExpand all lines: articles/communication-services/concepts/interop/tpe/teams-phone-extensibility-connectivity-cost.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -73,7 +73,7 @@ Teams licensing requirements vary based on the calling scenario when Teams Phone
73
73
74
74
### Outbound calling prerequisites
75
75
76
-
Starting **November 1, 2025**, Calling Plan licenses assigned to Teams Resource Accounts will no longer support On-Behalf-Of PSTN outbound calls or server-initiated outbound calls. A **[Pay-As-You-Go Calling Plan](/microsoftteams/calling-plans-for-office-365#pay-as-you-go-calling-plan)**and Communication Credits are required for these scenarios, based on the billing agreements.
76
+
Starting **November 1, 2025**, Calling Plan licenses assigned to Teams Resource Accounts will no longer support On-Behalf-Of PSTN outbound calls or server-initiated outbound calls. Customers now need a financing balance, which can be provided by a **[Communications Credits](/microsoftteams/set-up-communications-credits-for-your-organization)** license for legacy customers or telco overage for MCA customers. To activate a Communications Credits license, a **[Pay-As-You-Go Calling Plan](/microsoftteams/calling-plans-for-office-365#pay-as-you-go-calling-plan)**license is required as a prerequisite, since the Communications Credits license is an add-on. While telco overage can be set up without a PAYG license initially, the PAYG license must be acquired and assigned to the Resource Account for proper functionality. Therefore, customers must ensure the RA has a PAYG license along with either a Communications Credits license or telco overage.
77
77
78
78
> [!NOTE]
79
79
> Direct Routing numbers aren’t affected by these licensing changes.
@@ -89,7 +89,7 @@ The Greenplum linked service supports the following properties when apply versio
89
89
| port | The TCP port of the database server. The default value is `5432`.| No |
90
90
| database | The database to connect to. | Yes |
91
91
| username | The username to connect with. Not required if using IntegratedSecurity. |Yes |
92
-
|password| The password to connect with. Not required if using IntegratedSecurity. Mark this field as **SecureString** to store it securely. Or, you can [reference a secret stored in Azure Key Vault](store-credentials-in-key-vault.md). | Yes |
92
+
|pwd| The password to connect with. Not required if using IntegratedSecurity. Mark this field as **SecureString** to store it securely. Or, you can [reference a secret stored in Azure Key Vault](store-credentials-in-key-vault.md). | Yes |
93
93
| sslMode | Controls whether SSL is used, depending on server support. <br/>- **Disable**: SSL is disabled. If the server requires SSL, the connection will fail. <br/>- **Allow**: Prefer non-SSL connections if the server allows them, but allow SSL connections. <br/>- **Prefer**: Prefer SSL connections if the server allows them, but allow connections without SSL. <br/>- **Require**: Fail the connection if the server doesn't support SSL. <br/>- **Verify-ca**: Fail the connection if the server doesn't support SSL. Also verifies server certificate. <br/>- **Verify-full**: Fail the connection if the server doesn't support SSL. Also verifies server certificate with host's name. <br/> Options: Disable (0) / Allow (1) / Prefer (2) / Require (3) **(Default)** / Verify-ca (4) / Verify-full (5) | Yes |
94
94
| authenticationType | Authentication type for connecting to the database. Only supports **Basic**. | Yes |
95
95
| connectVia | The [Integration Runtime](concepts-integration-runtime.md) to be used to connect to the data store. Learn more from [Prerequisites](#prerequisites) section. If not specified, it uses the default Azure Integration Runtime. |No |
@@ -110,7 +110,7 @@ The Greenplum linked service supports the following properties when apply versio
110
110
"port": 5432,
111
111
"database": "<database>",
112
112
"username": "<username>",
113
-
"password": {
113
+
"pwd": {
114
114
"type": "SecureString",
115
115
"value": "<password>"
116
116
},
@@ -124,7 +124,7 @@ The Greenplum linked service supports the following properties when apply versio
124
124
}
125
125
}
126
126
```
127
-
**Example: store password in Azure Key Vault**
127
+
**Example: store pwd in Azure Key Vault**
128
128
```json
129
129
{
130
130
"name": "GreenplumLinkedService",
@@ -136,7 +136,7 @@ The Greenplum linked service supports the following properties when apply versio
136
136
"port": 5432,
137
137
"database": "<database>",
138
138
"username": "<username>",
139
-
"password": {
139
+
"pwd": {
140
140
"type": "AzureKeyVaultSecret",
141
141
"store": {
142
142
"referenceName": "<Azure Key Vault linked service name>",
Copy file name to clipboardExpand all lines: articles/sentinel/sap/deployment-solution-configuration.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -42,6 +42,9 @@ Before configuring the settings described in this article, you must have a Micro
42
42
43
43
For more information, see [Deploy the Microsoft Sentinel solution for SAP applications from the content hub](deploy-sap-security-content.md) and [Deploy Microsoft Sentinel solution for SAP applications](deployment-overview.md).
44
44
45
+
> [!TIP]
46
+
> Use the blog series "[How to successfully evaluate the SAP for Sentinel solution and implement it in production](https://techcommunity.microsoft.com/blog/microsoftsentinelblog/how-to-successfully-evaluate-the-sap-for-sentinel-solution-and-implement-it-in-p/4357962)" for a detailed walk through with best practices.
47
+
45
48
## Start enabling analytics rules
46
49
47
50
By default, all analytics rules in the Microsoft Sentinel solution for SAP applications are provided as [alert rule templates](../manage-analytics-rule-templates.md#manage-template-versions-for-your-scheduled-analytics-rules-in-microsoft-sentinel). We recommend a staged approach, where you use the templates to create a few rules at a time, allowing time for fine-tuning each scenario.
0 commit comments