Rename parameter causing conflicts

Author: Microsoft Graph DevX Tooling

src/NetworkAccess/NetworkAccess.md

@@ -0,0 +1,40 @@
+# NetworkAccess
+
+This directory contains common [AutoREST.PowerShell](https://github.com/Azure/autorest.powershell) configurations for NetworkAccess v1.0 and/or beta modules.
+
+## AutoRest Configuration
+
+> see <https://aka.ms/autorest>
+
+``` yaml
+require:
+  - $(this-folder)/../readme.graph.md
+```
+
+### Directives
+
+> see https://github.com/Azure/autorest/blob/master/docs/powershell/directives.md
+
+``` yaml
+directive:
+# Rename headers parameter provided in the open api file to avoid conflict with existing header property generated by Autorest for custom header support.
+  - where:
+      verb: New
+      subject: ^NetworkAccessLogTraffic$
+      variant: CreateExpanded
+      parameter-name: Headers
+    set:
+      parameter-name: AccessHeaders
+  - where:
+      verb: Update
+      subject: ^NetworkAccessLogTraffic$
+      variant: ^(UpdateExpanded|UpdateViaIdentityExpanded)$
+      parameter-name: Headers
+    set:
+      parameter-name: AccessHeaders
+# Parameter BodyParameter has multiple parameter types. 
+  - where:
+      verb: Update
+      subject: ^NetworkAccessForwardingPolicyRule$
+    remove: true
+```