Skip to content

Commit 30c6163

Browse files
Merge pull request #285077 from jojohpm/docs-editor/tutorial-improved-exports-1724172599
Update tutorial-improved-exports.md
2 parents fb331d5 + d81a849 commit 30c6163

File tree

1 file changed

+7
-2
lines changed

1 file changed

+7
-2
lines changed

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

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -180,16 +180,21 @@ Agreement types, scopes, and required roles are explained at [Understand and wor
180180

181181
The improved exports experience currently has the following limitations.
182182

183-
- The new exports experience doesn't fully support the management group scope and it has feature limitations.
183+
- The new exports experience doesn't fully support the management group scope, and it has feature limitations.
184+
184185
- Azure internal and MOSP billing scopes and subscriptions don’t support FOCUS datasets.
185186
- 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.
186187

187188
## FAQ
188189

189-
Why is file partitioning enabled in exports?
190+
#### Why is file partitioning enabled in exports?
190191

191192
The file partitioning is a feature that is activated by default to facilitate the management of large files. This functionality divides larger files into smaller segments, which enhances the ease of file transfer, download, ingestion, and overall readability. It's advantageous for customers whose cost files increase in size over time. The specifics of the file partitions are described in a manifest.json file provided with each export run, enabling you to rejoin the original file.
192193

194+
#### How does the enhanced export experience handle missing attributes like subscription IDs?
195+
196+
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.
197+
193198
## Next steps
194199

195200
- Learn more about exports at [Tutorial: Create and manage exported data](tutorial-export-acm-data.md).

0 commit comments

Comments
 (0)