Skip to content

Commit e64952d

Browse files
committed
MCM - Fix PR 290951
1 parent ede00ef commit e64952d

File tree

1 file changed

+18
-18
lines changed

1 file changed

+18
-18
lines changed

articles/cost-management-billing/costs/tutorial-improved-exports.md

Lines changed: 18 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Tutorial - Improved exports experience - Preview
33
description: This tutorial helps you create automatic exports for your actual and amortized costs in the Cost and Usage Specification standard (FOCUS) format.
44
author: jojohpm
55
ms.author: jojoh
6-
ms.date: 08/28/2024
6+
ms.date: 11/23/2024
77
ms.topic: tutorial
88
ms.service: cost-management-billing
99
ms.subservice: cost-management
@@ -185,7 +185,7 @@ The improved exports experience currently has the following limitations.
185185

186186
- Shared access service (SAS) key-based cross tenant export is only supported for Microsoft partners at the billing account scope. It isn't supported for other partner scenarios like any other scope, EA indirect contract, or Azure Lighthouse.
187187

188-
- EA price sheet: Reservation prices are only available for the current month price sheet and cannot be retrieved for historical exports. To retain historical reservation prices, set up recurring exports.
188+
- EA price sheet: Reservation prices are only available for the current month price sheet and can't be retrieved for historical exports. To retain historical reservation prices, set up recurring exports.
189189

190190
## FAQ
191191

@@ -195,15 +195,15 @@ The file partitioning is a feature that is activated by default to facilitate th
195195

196196
#### How does the enhanced export experience handle missing attributes like subscription IDs?
197197

198-
In the new export experience, missing attributes such as subscription IDs will be set to null or empty, rather than using a default empty GUID (00000000-0000-0000-0000-000000000000), to more accurately indicate the absence of a value. This affects charges pertaining to unused reservations, unused savings plan and rounding adjustments.
198+
In the new export experience, missing attributes such as subscription IDs are set to null or empty rather than using a default empty GUID (00000000-0000-0000-0000-000000000000). The null or empty values more accurately indicate the absence of a value. It affects charges pertaining to unused reservations, unused savings plan, and rounding adjustments.
199199

200200
#### How much historical data can I retrieve using Exports?
201201

202-
You can retrieve up to 13 months of historical data through the portal UI for all datasets, except for RI recommendations, which are limited to the current recommendation snapshot. To access data older than 13 months, you can use the REST API.
202+
You can retrieve up to 13 months of historical data through the Azure portal for all datasets, except for reservation recommendations, which are limited to the current recommendation snapshot. To access data older than 13 months, you can use the REST API.
203203

204-
- Cost and usage (Actual), Cost and usage (Amortized), Cost and usage (FOCUS): Up to 7 years of data.
204+
- Cost and usage (Actual), Cost and usage (Amortized), and Cost and usage (FOCUS): Up to seven years of data.
205205

206-
- Reservation transactions: Up to 7 years of data across all channels.
206+
- Reservation transactions: Up to seven years of data across all channels.
207207

208208
- Reservation recommendations, Reservation details: Up to 13 months of data.
209209

@@ -215,7 +215,7 @@ You can retrieve up to 13 months of historical data through the portal UI for al
215215

216216
#### Which datasets support Parquet format and compression?
217217

218-
The following table captures the supported formats and compression formats for each of the exported datasets. If you are creating an export with multiple datasets, Parquet & compression options will only appear in the dropdown if all of the selected datasets support them.
218+
The following table captures the supported formats and compression formats for each of the exported datasets. If you're creating an export with multiple datasets, Parquet & compression options only appear in the dropdown if all of the selected datasets support them.
219219

220220
|Dataset|Format supported|Compression supported|
221221
| -------- | -------- | -------- |
@@ -235,7 +235,7 @@ The following table captures the supported formats and compression formats for e
235235

236236
#### Why do I get the 'Unauthorized' error while trying to create an Export?
237237

238-
When attempting to create an Export to a storage account with a firewall, the user must have the Owner role or a custom role with `Microsoft.Authorization/roleAssignments/write` and `Microsoft.Authorization/permissions/read` permissions. If these permissions are missing, you will encounter an error like:
238+
When attempting to create an Export to a storage account with a firewall, the user must have the Owner role or a custom role with `Microsoft.Authorization/roleAssignments/write` and `Microsoft.Authorization/permissions/read` permissions. If these permissions are missing, you encounter an error similar to:
239239

240240

241241
```json
@@ -251,39 +251,39 @@ You can check for the permissions on the storage account by referring to the ste
251251

252252
#### What is the maximum number of subscriptions allowed within a management group (MG) when creating an export?
253253

254-
The maximum limit is **3000 subscriptions** per management group in Cost Management, including exports.
254+
The maximum limit is **3,000 subscriptions** per management group in Cost Management, including exports.
255255

256-
To manage more than 3000 subscriptions:
256+
To manage more than 3,000 subscriptions:
257257

258-
- Organize them into smaller management groups. For example, if you have a total of 12,500 subscriptions, create 5 management groups with approximately 2,500 subscriptions each. Create separate exports for each management group scope and combine the exported data for a complete view.
258+
- Organize them into smaller management groups. For example, if you have a total of 12,500 subscriptions, create five management groups with approximately 2,500 subscriptions each. Create separate exports for each management group scope and combine the exported data for a complete view.
259259

260260
- Alternatively, if all subscriptions are under the same billing account, create an export at the **billing account scope** to get combined data.
261261

262262
#### How are the exported files organized in the blob storage folders?
263263

264264
The exported files are organized in a structured hierarchy within the storage folders. The naming and hierarchy of the folders are as follows:
265265

266-
- StorageContainer/StorageDirectory/ExportName/[YYYYMMDD-YYYYMMDD]/[RunID]/
266+
- `StorageContainer/StorageDirectory/ExportName/[YYYYMMDD-YYYYMMDD]/[RunID]/`
267267

268268
This path contains the CSV files and a manifest file.
269269

270270
For example:
271271

272-
- StorageContainer/StorageDirectory/ExportName/[20240401-20240430]/[RunID1]/
272+
- `StorageContainer/StorageDirectory/ExportName/[20240401-20240430]/[RunID1]/`
273273

274274
This folder contains the CSV files and the manifest file for all export runs during the April 2024 time period.
275275

276-
- StorageContainer/StorageDirectory/ExportName/[20241101-20241130]/[RunID2]/
276+
- `StorageContainer/StorageDirectory/ExportName/[20241101-20241130]/[RunID2]/`
277277

278278
This folder contains the CSV files and the manifest file for all export runs during the November 2024 time period.
279279

280-
We ensure that the cost file for a particular month is available within that month's folder (e.g., [20240401-20240430], [20241101-20241130], etc.).
280+
Azure ensures that the cost file for a particular month is available within that month's folder. For example, `[20240401-20240430]`, `[20241101-20241130]` and so on.
281281

282-
- **Without file overwrite:** You will see multiple RunIDs within the month folder, representing different export runs (e.g., 30 different RunIDs for 30 days).
282+
- **Without file overwrite:** You see multiple *RunIDs* within the month folder, representing different export runs. For example, 30 different *RunIDs* for 30 days.
283283

284-
- **With file overwrite:** You will see only one RunID within the month folder, representing the latest run.
284+
- **With file overwrite:** You see only one *RunID* within the month folder, representing the latest run.
285285

286-
At the time of export creation, you can name the StorageContainer, StorageDirectory, and ExportName.
286+
At the time of export creation, you can name the *StorageContainer*, *StorageDirectory*, and *ExportName*.
287287

288288
## Next steps
289289

0 commit comments

Comments
 (0)