Fix bicep export functionality: resolve build errors and update documentation

- Fix FileUtility.cs: Add missing XML documentation for extension parameter
- Fix FileUtility.cs: Use dynamic extension parameter instead of hardcoded .json
- Update ChangeLog.md: Add bicep export feature entry for upcoming release
- Update Export-AzResourceGroup.md: Add OutputFormat parameter documentation and examples
- Add TestExportResourceGroupBicep.json: New test recording file for bicep export tests
- Update existing test recording files with latest test runs

Addresses PR review feedback regarding missing documentation and changelog updates.
All build errors resolved and functionality verified.

Author: anamikapan

src/Resources/ResourceManager/Utilities/FileUtility.cs

@@ -35,8 +35,9 @@ public static class FileUtility
         /// <param name="outputPath">The file output path</param>
         /// <param name="overwrite">Overrides existing file</param>
         /// <param name="shouldContinue">The confirmation action</param>
+        /// <param name="extension">The file extension (defaults to .json)</param>
         /// <returns>The file path</returns>
-        public static string SaveTemplateFile(string templateName, string contents, string outputPath, bool overwrite, Func<string, string, bool> shouldContinue, string extension = ".json") // Added extension parameter with default
+        public static string SaveTemplateFile(string templateName, string contents, string outputPath, bool overwrite, Func<string, string, bool> shouldContinue, string extension = ".json")
         {
             StringBuilder finalOutputPath = new StringBuilder();
 
@@ -48,14 +49,14 @@ public static class FileUtility
 
             if (FileUtilities.IsValidDirectoryPath(outputPath))
             {
-                finalOutputPath.Append(Path.Combine(outputPath, templateName + ".json"));
+                finalOutputPath.Append(Path.Combine(outputPath, templateName + extension));
             }
             else
             {
                 finalOutputPath.Append(outputPath);
-                if (!outputPath.EndsWith(".json"))
+                if (!outputPath.EndsWith(extension))
                 {
-                    finalOutputPath.Append(".json");
+                    finalOutputPath.Append(extension);
                 }
             }
 

src/Resources/Resources.Test/SessionRecords/Microsoft.Azure.Commands.Resources.Test.ScenarioTests.ResourceGroupTests/TestExportResourceGroup.json

@@ -19,6 +19,9 @@
 -->
 
 ## Upcoming Release
+* Added support for exporting resource group templates as Bicep files
+    - Added `OutputFormat` parameter to `Export-AzResourceGroup` cmdlet
+    - Supported values: `Json` (default), `Bicep`
 
 ## Version 8.0.1
 * Fixed empty warning output issue for cmdlet `Test-AzResourceGroupDeployment` [#27888]

src/Resources/Resources.Test/SessionRecords/Microsoft.Azure.Commands.Resources.Test.ScenarioTests.ResourceGroupTests/TestExportResourceGroupAsyncRoute.json

@@ -16,12 +16,12 @@ Captures a resource group as a template and saves it to a file.
 ```
 Export-AzResourceGroup -ResourceGroupName <String> [-Path <String>] [-IncludeParameterDefaultValue]
  [-IncludeComments] [-SkipResourceNameParameterization] [-SkipAllParameterization] [-Resource <String[]>]
- [-Force] [-ApiVersion <String>] [-Pre] [-DefaultProfile <IAzureContextContainer>]
+ [-OutputFormat <String>] [-Force] [-ApiVersion <String>] [-Pre] [-DefaultProfile <IAzureContextContainer>]
  [-WhatIf] [-Confirm] [<CommonParameters>]
 ```
 
 ## DESCRIPTION
-The **Export-AzResourceGroup** cmdlet captures the specified resource group as a template and saves it to a JSON file.This can be useful in scenarios where you have already created some resources in your resource group, and then want to leverage the benefits of using template backed deployments.
+The **Export-AzResourceGroup** cmdlet captures the specified resource group as a template and saves it to a JSON or Bicep file.This can be useful in scenarios where you have already created some resources in your resource group, and then want to leverage the benefits of using template backed deployments.
 This cmdlet gives you an easy start by generating the template for your existing resources in the resource group.
 There might be some cases where this cmdlet fails to generate some parts of the template.
 Warning messages will inform you of the resources that failed.
@@ -53,6 +53,20 @@ Export-AzResourceGroup -ResourceGroupName "TestGroup" -SkipAllParameterization -
 
 This command captures two resources from the "TestGroup" resource group as a template, and saves it to a JSON file in the current directory. The generated template will not contain any generated parameters.
 
+### Example 4: Export a resource group as a Bicep file
+```powershell
+Export-AzResourceGroup -ResourceGroupName "TestGroup" -OutputFormat Bicep
+```
+
+This command captures the resource group named TestGroup as a template, and saves it to a Bicep file in the current directory.
+
+### Example 5: Export a resource group as a Bicep file with custom path
+```powershell
+Export-AzResourceGroup -ResourceGroupName "TestGroup" -OutputFormat Bicep -Path "C:\Templates\MyResourceGroup.bicep"
+```
+
+This command captures the resource group named TestGroup as a template, and saves it to a Bicep file at the specified path.
+
 ## PARAMETERS
 
 ### -ApiVersion
@@ -146,6 +160,21 @@ Accept pipeline input: True (ByPropertyName)
 Accept wildcard characters: False
 ```
 
+### -OutputFormat
+Specifies the format of the exported template. Supported values are "Json" and "Bicep".
+
+```yaml
+Type: System.String
+Parameter Sets: (All)
+Aliases:
+
+Required: False
+Position: Named
+Default value: Json
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
 ### -Pre
 Indicates that this cmdlet use pre-release API versions when automatically determining which API version to use.