Skip to content

Commit dfe2027

Browse files
committed
Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into 1606477-clarify-string
2 parents 2ab776a + 89420e0 commit dfe2027

File tree

7 files changed

+168
-120
lines changed

7 files changed

+168
-120
lines changed

articles/active-directory/manage-apps/use-scim-to-provision-users-and-groups.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.workload: identity
1212
ms.tgt_pltfrm: na
1313
ms.devlang: na
1414
ms.topic: conceptual
15-
ms.date: 07/31/2019
15+
ms.date: 10/01/2019
1616
ms.author: mimart
1717
ms.reviewer: arvinh
1818
ms.custom: aaddev;it-pro;seohack1

articles/azure-monitor/app/troubleshoot-faq.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.service: application-insights
1010
ms.workload: mobile
1111
ms.tgt_pltfrm: ibiza
1212
ms.topic: conceptual
13-
ms.date: 12/17/2018
13+
ms.date: 09/16/2019
1414
ms.author: mbullwin
1515
---
1616
# Application Insights: Frequently Asked Questions
@@ -53,7 +53,7 @@ The Enterprise plan incurs a charge for each day that each web server node sends
5353

5454
[Read the pricing plan](https://azure.microsoft.com/pricing/details/application-insights/).
5555

56-
## How much is it costing?
56+
## How much does it cost?
5757

5858
* Open the **Usage and estimated costs page** in an Application Insights resource. There's a chart of recent usage. You can set a data volume cap, if you want.
5959
* Open the [Azure Billing blade](https://portal.azure.com/#blade/Microsoft_Azure_Billing/BillingBlade/Overview) to see your bills across all resources.
@@ -133,6 +133,8 @@ We look up the IP address (IPv4 or IPv6) of the web client using [GeoLite2](http
133133

134134
* Browser telemetry: We collect the sender's IP address.
135135
* Server telemetry: The Application Insights module collects the client IP address. It is not collected if `X-Forwarded-For` is set.
136+
* To learn more about how IP address and geolocation data is collected in Application Insights refer to this [article](https://docs.microsoft.com/azure/azure-monitor/app/ip-collection).
137+
136138

137139
You can configure the `ClientIpHeaderTelemetryInitializer` to take the IP address from a different header. In some systems, for example, it is moved by a proxy, load balancer, or CDN to `X-Originating-IP`. [Learn more](https://apmtips.com/blog/2016/07/05/client-ip-address/).
138140

articles/network-watcher/network-watcher-connectivity-powershell.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ $RG = Get-AzResourceGroup -Name $rgName
5353
$VM1 = Get-AzVM -ResourceGroupName $rgName | Where-Object -Property Name -EQ $sourceVMName
5454
$VM2 = Get-AzVM -ResourceGroupName $rgName | Where-Object -Property Name -EQ $destVMName
5555
56-
$networkWatcher = Get-AzResource | Where {$_.ResourceType -eq "Microsoft.Network/networkWatchers" -and $_.Location -eq $VM1.Location}
56+
$networkWatcher = Get-AzNetworkWatcher | Where-Object -Property Location -EQ -Value $VM1.Location
5757
5858
Test-AzNetworkWatcherConnectivity -NetworkWatcher $networkWatcher -SourceId $VM1.Id -DestinationId $VM2.Id -DestinationPort 80
5959
```
@@ -144,7 +144,7 @@ $sourceVMName = "MultiTierApp0"
144144
$RG = Get-AzResourceGroup -Name $rgName
145145
$VM1 = Get-AzVM -ResourceGroupName $rgName | Where-Object -Property Name -EQ $sourceVMName
146146
147-
$networkWatcher = Get-AzResource | Where {$_.ResourceType -eq "Microsoft.Network/networkWatchers" -and $_.Location -eq $VM1.Location }
147+
$networkWatcher = Get-AzNetworkWatcher | Where-Object -Property Location -EQ -Value $VM1.Location
148148
149149
Test-AzNetworkWatcherConnectivity -NetworkWatcher $networkWatcher -SourceId $VM1.Id -DestinationAddress 13.107.21.200 -DestinationPort 80
150150
```
@@ -207,7 +207,7 @@ $sourceVMName = "MultiTierApp0"
207207
$RG = Get-AzResourceGroup -Name $rgName
208208
$VM1 = Get-AzVM -ResourceGroupName $rgName | Where-Object -Property Name -EQ $sourceVMName
209209
210-
$networkWatcher = Get-AzResource | Where {$_.ResourceType -eq "Microsoft.Network/networkWatchers" -and $_.Location -eq $VM1.Location }
210+
$networkWatcher = Get-AzNetworkWatcher | Where-Object -Property Location -EQ -Value $VM1.Location
211211
212212
213213
Test-AzNetworkWatcherConnectivity -NetworkWatcher $networkWatcher -SourceId $VM1.Id -DestinationAddress https://bing.com/
@@ -260,7 +260,7 @@ $RG = Get-AzResourceGroup -Name $rgName
260260
261261
$VM1 = Get-AzVM -ResourceGroupName $rgName | Where-Object -Property Name -EQ $sourceVMName
262262
263-
$networkWatcher = Get-AzResource | Where {$_.ResourceType -eq "Microsoft.Network/networkWatchers" -and $_.Location -eq $VM1.Location }
263+
$networkWatcher = Get-AzNetworkWatcher | Where-Object -Property Location -EQ -Value $VM1.Location
264264
265265
Test-AzNetworkWatcherConnectivity -NetworkWatcher $networkWatcher -SourceId $VM1.Id -DestinationAddress https://contosostorageexample.blob.core.windows.net/
266266
```
@@ -302,4 +302,4 @@ Hops : [
302302

303303
Determine whether certain traffic is allowed in or out of your VM by visiting [Check IP flow verify](diagnose-vm-network-traffic-filtering-problem.md).
304304

305-
If traffic is being blocked and it should not be, see [Manage Network Security Groups](../virtual-network/manage-network-security-group.md) to track down the network security group and security rules that are defined.
305+
If traffic is being blocked and it should not be, see [Manage Network Security Groups](../virtual-network/manage-network-security-group.md) to track down the network security group and security rules that are defined.

articles/storage/blobs/TOC.yml

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -135,13 +135,15 @@
135135
href: ../common/storage-disaster-recovery-guidance.md?toc=%2fazure%2fstorage%2fblobs%2ftoc.json
136136
- name: Designing HA Apps using RA-GRS
137137
href: ../common/storage-designing-ha-apps-with-ragrs.md?toc=%2fazure%2fstorage%2fblobs%2ftoc.json
138-
- name: Access tiers
138+
- name: Access and performance tiers
139139
items:
140140
- name: Access tiers
141141
href: storage-blob-storage-tiers.md
142-
- name: Rehydrate data from Archive Storage
142+
- name: Rehydrate data from archive tier
143143
href: storage-blob-rehydration.md
144-
- name: Managing the Azure Blob Storage Lifecycle
144+
- name: Performance tiers
145+
href: storage-blob-performance-tiers.md
146+
- name: Manage the Azure Blob storage lifecycle
145147
href: storage-lifecycle-management-concepts.md
146148
- name: Performance and scaling
147149
items:
Lines changed: 62 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,62 @@
1+
---
2+
title: Azure Block Blob storage performance tiers - Azure Storage
3+
description: Performance tiers for Azure blob storage.
4+
author: mhopkins-msft
5+
6+
ms.author: mhopkins
7+
ms.date: 10/02/2019
8+
ms.service: storage
9+
ms.subservice: blobs
10+
ms.topic: conceptual
11+
ms.reviewer: clausjor
12+
---
13+
14+
# Azure Block Blob storage performance tiers
15+
16+
As enterprises deploy performance sensitive cloud-native applications, it's important to have options for cost-effective data storage at different performance levels.
17+
18+
Azure block blob storage offers two different performance tiers:
19+
20+
- Premium: optimized for high transaction rates and single-digit consistent storage latency
21+
- Standard: optimized for high capacity and high throughput
22+
23+
The following considerations apply to the different performance tiers:
24+
25+
- Standard performance is available in all [Azure regions](https://azure.microsoft.com/global-infrastructure/services/?products=storage). Premium performance is available in [select regions](https://azure.microsoft.com/global-infrastructure/services/?products=storage).
26+
- Premium performance provides optimized pricing for applications with high transaction rates to help [lower total storage cost](https://azure.microsoft.com/blog/reducing-overall-storage-costs-with-azure-premium-blob-storage/) for these workloads.
27+
- Premium performance requires using block blob storage accounts, which support block blob and append blob.
28+
- Standard performance is available with General Purpose v1, General Purpose v2, and Blob storage accounts.
29+
- Premium and standard performance both support [high throughput block blobs](https://azure.microsoft.com/blog/high-throughput-with-azure-blob-storage/). High throughput block blobs are available for premium performance at greater than 256 KiB. High throughput block blobs are available for standard performance at greater than 4 MiB Put Block or Put Blob sizes.
30+
- Premium performance is currently available with locally redundant storage (LRS) only.
31+
32+
## Premium performance
33+
34+
Premium performance block blob storage makes data available via high-performance hardware. Data is stored on solid-state drives (SSDs) which are optimized for low latency. SSDs provide higher throughput compared to traditional hard drives.
35+
36+
Premium performance block blob storage is ideal for workloads that require fast and consistent response times. It's best for workloads that perform many small transactions.
37+
38+
## Standard performance
39+
40+
Standard performance supports different [access tiers](storage-blob-storage-tiers.md) to store data in the most cost-effective manner. It's optimized for high capacity and high throughput on large data sets.
41+
42+
## Blob lifecycle management
43+
44+
Blob Storage lifecycle management offers a rich, rule-based policy:
45+
46+
- Premium - expire data at the end of its lifecycle
47+
- Standard - transition data to the best access tier and expire data at the end of its lifecycle
48+
49+
To learn more, see [Manage the Azure Blob storage lifecycle](storage-lifecycle-management-concepts.md).
50+
51+
Data that's stored in a premium block blob storage account can't be moved between hot, cool, and archive tiers. However, you can copy blobs from a block blob storage account to the hot access tier in a *different* account. Use the [Put Block From URL](/rest/api/storageservices/put-block-from-url) API or [AzCopy v10](../common/storage-use-azcopy-v10.md) to copy data to a different account. The **Put Block From URL** API synchronously copies data on the server. The call completes only after all the data is moved from the original server location to the destination location.
52+
53+
## Next steps
54+
55+
Evaluate hot, cool, and archive in GPv2 and Blob storage accounts
56+
57+
- [Check availability of hot, cool, and archive by region](https://azure.microsoft.com/regions/#services)
58+
- [Manage the Azure Blob storage lifecycle](storage-lifecycle-management-concepts.md)
59+
- [Learn about rehydrating blob data from the archive tier](storage-blob-rehydration.md)
60+
- [Evaluate usage of your current storage accounts by enabling Azure Storage metrics](../common/storage-enable-and-view-metrics.md)
61+
- [Check hot, cool, and archive pricing in Blob storage and GPv2 accounts by region](https://azure.microsoft.com/pricing/details/storage/)
62+
- [Check data transfers pricing](https://azure.microsoft.com/pricing/details/data-transfers/)

0 commit comments

Comments
 (0)