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/active-directory/hybrid/connect/how-to-upgrade-previous-version.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
@@ -37,7 +37,7 @@ There are a few different strategies that you can use to upgrade Azure AD Connec
37
37
| Method | Description | Pros | Cons |
38
38
| --- | --- | --- | --- |
39
39
|[Automatic upgrade](how-to-connect-install-automatic-upgrade.md)|This is the easiest method for customers with an express installation |No manual intervention |Auto-upgrade version might not include the latest features |
40
-
|[In-place upgrade](#in-place-upgrade)|If you have a single server, you can upgrade the installation in-place on the same server |Doesn't require another server|If there's an issue while in-place upgrading, you can't roll back the new release or configuration and change the active server when you are ready |Safest approach and smoother transition to a newer version. Supports Windows OS (Operating Systems) upgrade. Sync is not interrupted and doesn't impose a risk to production |Requires another server|
40
+
|[In-place upgrade](#in-place-upgrade)|If you have a single server, you can upgrade the installation in-place on the same server |- Doesn't require another server<br/><br/> - Safest approach and smoother transition to a newer version. Supports Windows OS (Operating Systems) upgrade. Sync is not interrupted and doesn't impose a risk to production |- If there's an issue while in-place upgrading, you can't roll back the new release or configuration and change the active server when you are ready <br/><br/>- Requires another server|
41
41
42
42
For permissions information, see the [permissions required for an upgrade](reference-connect-accounts-permissions.md#upgrade).
Copy file name to clipboardExpand all lines: articles/azure-health-insights/trial-matcher/transparency-note.md
+7-6Lines changed: 7 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,12 +27,13 @@ Organizations can use the Trial Matcher model to match patients to potentially s
27
27
28
28
29
29
### Key terms
30
-
| Term | What is it |||||
31
-
|----------|--|--|--|--|--|
32
-
| Patient centric | Trial Matcher, when powering a single patient trial search, helps a patient narrow down the list of potentially suitable clinical trials based on the patient’s clinical information. ||
33
-
| Trial centric | Trial Matcher, when powering search for eligible patients to clinical trial, is provided with list of clinical trials (one or more) and multiple patients’ information. The model is using the matching technology to find which patients could potentially be suitable for each trial. ||
34
-
| Evidence | For each trial that the model concludes the patient is not eligible for, the model returns the relevant patient information and the eligibility criteria that the model used to exclude the patient from trial eligibility. ||
35
-
| Gradual matching | The model can provide patient information with gradual matching. In this mode, the user can send requests to Trial Matcher gradually, primarily via conversational intelligence or chat-like scenarios. ||
30
+
31
+
| Term | What is it |
32
+
|----------|---------------|
33
+
| Patient centric | Trial Matcher, when powering a single patient trial search, helps a patient narrow down the list of potentially suitable clinical trials based on the patient’s clinical information. |
34
+
| Trial centric | Trial Matcher, when powering search for eligible patients to clinical trial, is provided with list of clinical trials (one or more) and multiple patients’ information. The model is using the matching technology to find which patients could potentially be suitable for each trial. |
35
+
| Evidence | For each trial that the model concludes the patient is not eligible for, the model returns the relevant patient information and the eligibility criteria that the model used to exclude the patient from trial eligibility. |
36
+
| Gradual matching | The model can provide patient information with gradual matching. In this mode, the user can send requests to Trial Matcher gradually, primarily via conversational intelligence or chat-like scenarios. |
Copy file name to clipboardExpand all lines: articles/azure-netapp-files/performance-oracle-multiple-volumes.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -83,7 +83,7 @@ After scaling limits were tested with SLOB2, tests were conducted with a real-wo
83
83
84
84
This database has significant extra IO going on in addition to the application workload due to flashback being enabled and has a database block size of 16k. From the IO profile section of the AWR report, it's apparent that there is a heavy ratio of writes in comparison to reads.
85
85
86
-
|| Read and write per second | Read per second | Write per second |
86
+
|- | Read and write per second | Read per second | Write per second |
87
87
| - | -- | -- | -- |
88
88
| Total (MB) | 4,988.1 | 1,395.2 | 3,592.9 |
89
89
@@ -216,7 +216,7 @@ All Oracle required system configuration settings for version 19c were implement
216
216
217
217
The following parameters were added to the `/etc/sysctl.conf` Linux system file:
218
218
* `sunrpc.max_tcp_slot_table_entries: 128`
219
-
* `sunrpc.tcp_slot_table_entries = 128`
219
+
* `sunrpc.tcp_slot_table_entries = 128`
220
220
221
221
### Azure NetApp Files
222
222
@@ -362,6 +362,6 @@ Microsoft Oracle subject matter experts have estimated that more than 80% of Ora
362
362
* [Run Your Most Demanding Oracle Workloads in Azure without Sacrificing Performance or Scalability](https://techcommunity.microsoft.com/t5/azure-architecture-blog/run-your-most-demanding-oracle-workloads-in-azure-without/ba-p/3264545)
363
363
* [Solution architectures using Azure NetApp Files - Oracle](azure-netapp-files-solution-architectures.md#oracle)
364
364
* [Design and implement an Oracle database in Azure](../virtual-machines/workloads/oracle/oracle-design.md)
365
-
* [Estimate Tool for Sizing Oracle Workloads to Azure IaaS VMs](https://techcommunity.microsoft.com/t5/data-architecture-blog/estimate-tool-for-sizing-oracle-workloads-to-azure-iaas-vms/ba-p/1427183)
365
+
* [Estimate Tool for Sizing Oracle Workloads to Azure IaaS VMs](https://techcommunity.microsoft.com/t5/data-architecture-blog/estimate-tool-for-sizing-oracle-workloads-to-azure-iaas-vms/ba-p/1427183)
366
366
* [Reference architectures for Oracle Database Enterprise Edition on Azure](../virtual-machines/workloads/oracle/oracle-reference-architecture.md)
367
367
* [Understand Azure NetApp Files application volumes groups for SAP HANA](application-volume-group-introduction.md)
Copy file name to clipboardExpand all lines: articles/backup/backup-azure-reports-data-model.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -253,11 +253,11 @@ This table provides details about policy-related fields.
253
253
| ScheduleWindowDuration | Integer | Recovery Services vault | Duration of the daily window in which backups can be run. Applicable for enhanced policy for Azure VM backup |
254
254
| ScheduleWindowStartTime | DateTime | Recovery Services vault | Start time of the daily window in which backups can be run. Applicable for enhanced policy for Azure VM backup |
255
255
| FullBackupDaysOfTheWeek | String | Backup vault | Days of the week when full backup runs. Currently applicable for Azure PostgreSQL backup |
256
-
| FullBackupFrequency | String | Backup vault | Frequency of full backup. Currently applicable for Azure PostgreSQL backup ||
257
-
| FullBackupTimes | String | Backup vault | Time of the day at which full backup is taken. Currently applicable for Azure PostgreSQL backup ||
256
+
| FullBackupFrequency | String | Backup vault | Frequency of full backup. Currently applicable for Azure PostgreSQL backup |
257
+
| FullBackupTimes | String | Backup vault | Time of the day at which full backup is taken. Currently applicable for Azure PostgreSQL backup |
258
258
| IncrementalBackupDaysOfTheWeek | String | Backup vault | Days of the week when incremental backup runs. Currently applicable for Azure Disk backup |
259
259
| IncrementalBackupFrequency | String | Backup vault | Frequency of incremental backup. Currently applicable for Azure Disk backup |
260
-
| IncrementalBackupTimes | String | Backup vault | Time of the day at which incremental backup is taken. Currently applicable for Azure Disk backup ||
260
+
| IncrementalBackupTimes | String | Backup vault | Time of the day at which incremental backup is taken. Currently applicable for Azure Disk backup |
261
261
| PolicyId | String | Backup vault | Azure Resource Manager (ARM) ID of the backup policy |
262
262
| SnapshotTierDailyRetentionDuration | Integer | Backup vault | Retention duration in days for daily snapshots. Applicable for Azure Blob and Azure Disk backup |
263
263
| SnapshotTierWeeklyRetentionDuration | Integer | Backup vault | Retention duration in weeks for weekly snapshots. Applicable for Azure Blob and Azure Disk backup |
Copy file name to clipboardExpand all lines: articles/ddos-protection/ddos-view-diagnostic-logs.md
+13-11Lines changed: 13 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -47,8 +47,8 @@ In this tutorial, you learn how to:
47
47
Notifications will notify you anytime a public IP resource is under attack, and when attack mitigation is over.
48
48
49
49
```kusto
50
-
AzureDiagnostics
51
-
| where Category == "DDoSProtectionNotifications"
50
+
AzureDiagnostics
51
+
| where Category == "DDoSProtectionNotifications"
52
52
```
53
53
54
54
@@ -73,8 +73,8 @@ The following table lists the field names and descriptions:
73
73
Attack mitigation flow logs allow you to review the dropped traffic, forwarded traffic and other interesting data-points during an active DDoS attack in near-real time. You can ingest the constant stream of this data into Microsoft Sentinel or to your third-party SIEM systems via event hub for near-real time monitoring, take potential actions and address the need of your defense operations.
74
74
75
75
```kusto
76
-
AzureDiagnostics
77
-
| where Category == "DDoSMitigationFlowLogs"
76
+
AzureDiagnostics
77
+
| where Category == "DDoSMitigationFlowLogs"
78
78
```
79
79
80
80
The following table lists the field names and descriptions:
@@ -101,8 +101,8 @@ The following table lists the field names and descriptions:
101
101
Attack mitigation reports use the Netflow protocol data, which is aggregated to provide detailed information about the attack on your resource. Anytime a public IP resource is under attack, the report generation will start as soon as the mitigation starts. There will be an incremental report generated every 5 mins and a post-mitigation report for the whole mitigation period. This is to ensure that in an event the DDoS attack continues for a longer duration of time, you'll be able to view the most current snapshot of mitigation report every 5 minutes and a complete summary once the attack mitigation is over.
102
102
103
103
```kusto
104
-
AzureDiagnostics
105
-
| where Category == "DDoSMitigationReports"
104
+
AzureDiagnostics
105
+
| where Category == "DDoSMitigationReports"
106
106
```
107
107
108
108
The following table lists the field names and descriptions:
@@ -120,22 +120,24 @@ The following table lists the field names and descriptions:
120
120
|**ReportType**| Possible values are `Incremental` and `PostMitigation`. |
121
121
|**MitigationPeriodStart**| The date and time in UTC when the mitigation started. |
122
122
|**MitigationPeriodEnd**| The date and time in UTC when the mitigation ended. |
123
-
|**IPAddress**| Your public IP Address. |
123
+
|**IPAddress**| Your public IP Address. |
124
124
|**AttackVectors**| Degradation of attack types. The keys include `TCP SYN flood`, `TCP flood`, `UDP flood`, `UDP reflection`, and `Other packet flood`. |
125
-
| **TrafficOverview** | Degradation of attack traffic. The keys include `Total packets`, `Total packets dropped`, `Total TCP packets`, `Total TCP packets dropped`, `Total UDP packets`, `Total UDP packets dropped`, `Total Other packets`, and `Total Other packets dropped`. |
126
-
| **Protocols** | Breakdown of protocols included. The keys include `TCP`, `UDP`, and `Other`. |
125
+
|**TrafficOverview**| Degradation of attack traffic. The keys include `Total packets`, `Total packets dropped`, `Total TCP packets`, `Total TCP packets dropped`, `Total UDP packets`, `Total UDP packets dropped`, `Total Other packets`, and `Total Other packets dropped`. |
126
+
|**Protocols**| Breakdown of protocols included. The keys include `TCP`, `UDP`, and `Other`. |
127
127
|**DropReasons**| Analysis of causes of dropped packets. The keys include `Protocol violation invalid TCP`. `syn Protocol violation invalid TCP`, `Protocol violation invalid UDP`, `UDP reflection`, `TCP rate limit exceeded`, `UDP rate limit exceeded`, `Destination limit exceeded`, `Other packet flood Rate limit exceeded`, and `Packet was forwarded to service`. Protocol violation invalid drop reasons refer to malformed packets. |
128
128
|**TopSourceCountries**| Breakdown of the top 10 source countries into inbound traffic. |
129
129
|**TopSourceCountriesForDroppedPackets**| Analysis of the top 10 source countries for attack traffic that have been throttled. |
130
-
| **TopSourceASNs** | Analysis of the top 10 sources of autonomous system numbers (ASNs) of incoming traffic. |
130
+
|**TopSourceASNs**| Analysis of the top 10 sources of autonomous system numbers (ASNs) of incoming traffic. |
131
131
|**SourceContinents**| Analysis of the source continent for inbound traffic. |
132
132
|**Type**| Type of notification. Possible values include `MitigationStarted`. `MitigationStopped`. |
133
133
134
134
135
135
## Next steps
136
136
137
-
In this tutorial you learned how to view DDoS Protection diagnostic logs in a Log Analytics workspace. To learn more about the recommended steps to take when you receive a DDoS attack, see these next steps.
137
+
In this tutorial, you learned how to view DDoS Protection diagnostic logs in a Log Analytics workspace. To learn more about the recommended steps to take when you receive a DDoS attack, see these next steps.
138
138
139
139
> [!div class="nextstepaction"]
140
140
> [Engage with Azure DDoS Rapid Response](ddos-rapid-response.md)
141
+
142
+
> [!div class="nextstepaction"]
141
143
> [components of a DDoS Rapid Response Strategy](ddos-response-strategy.md)
![prmerger-automator[bot]](https://avatars.githubusercontent.com/u/22479449?v=4&size=40){kind=avatar}
0 commit comments