Merge pull request #261314 from andreamichaelmsft/patch-8

Add ConnectivityConfigurationChange schema info

Author: prmerger-automator[bot]

articles/virtual-network-manager/concept-event-logs.md

@@ -21,8 +21,12 @@ Azure Virtual Network Manager currently provides the following log categories:
     - Track when a particular virtual network’s network group membership is modified. In other words, a log is emitted when a virtual network is added to or removed from a network group. This can be used to trace network group membership changes over time and to capture a snapshot of a particular virtual network’s network group membership.
 - Rule collection change
     - Track when a particular virtual network’s set of applied security admin rule collections changes. A log is emitted for every rule collection deployed to a virtual network via the network group the rule collection is targeting. Any removal of a rule collection from a network group through a deployment process will also result in a log for each affected virtual network. This schema can be used to track what rule collection(s) have been deployed to a particular virtual network over time.
-    - If a virtual network is receiving security admin rule collection(s) from multiple network managers, logs will be emitted separately for each network manager for their respective rule collection changes.
+    - If a virtual network is receiving security admin rule collections from multiple network managers, logs will be emitted separately for each network manager for their respective rule collection changes.
     - If a virtual network is added to or removed from a network group that already has a rule collection(s) deployed onto it, a log will be emitted for that virtual network showing the state of applied rule collection(s).
+- Connectivity configuration change
+    - Track when a particular virtual network's applied connectivity configuration(s) changes. A log is emitted for every connectivity configuration deployed to a virtual network via the network group the configuration is targeting. Any removal of a connectivity configuration from a network group or vice versa through a deployment process will also result in a log for each affected virtual network. This schema can be used to track what connectivity configuration(s) and their respective topology types have been deployed to a particular virtual network over time.
+    - If a virtual network is receiving connectivity configurations from multiple network managers, logs will be emitted separately for each network manager for their respective configuration changes.
+    - If a virtual network is added to or removed from a network group that already has a connectivity configuration(s) deployed onto it, a log will be emitted for that virtual network showing the state of applied connectivity configuration(s).
 
 ## Network group membership change attributes 
 
@@ -89,6 +93,37 @@ Within the `properties` attribute are several nested attributes:
 | Message | A static message stating if a rule collection change was successful or unsuccessful. |
 | AppliedRuleCollectionIds | Collection of what security admin rule collections are applied to the virtual network at the time the log was emitted. There may be multiple rule collection IDs listed since a virtual network can belong to multiple network groups and have multiple rule collections applied simultaneously. |
 
+## Connectivity configuration change attributes
+
+This category emits one log per connectivity configuration change per virtual network. So, when a connectivity configuration is applied to or removed from a virtual network through its network group, a log is emitted correlating to that change in connectivity configuration set for that particular virtual network. The following attributes correspond to the logs that would be sent to your storage account; Log Analytics logs will have slightly different attributes.
+
+| Attribute | Description |
+|-----------|-------------|
+| time | Datetime when the event was logged. |
+| resourceId | Resource ID of the network manager. |
+| location | Location of the virtual network resource. |
+| operationName | Operation that resulted in the virtual network being added or removed. Always the Microsoft.Network/networkManagers/connectivityConfigurations/write operation. |
+| category | Category of this log. Always ConnectivityConfigurationChange. |
+| resultType | Indicates successful or failed operation. |
+| correlationId | GUID that can help relate or debug logs. |
+| level | Always Info. |
+| properties | Collection of properties of the log. |
+
+Within the `properties` attribute are several nested attributes:
+
+| properties attributes | Description |
+|--------------------|-------------|
+| AppliedConnectivityConfigurations | Collection of what connectivity configuration(s) are applied to the virtual network at the time the log was emitted. There may be multiple connectivity configurations listed since a network group can have multiple connectivity configurations applied simultaneously, and a virtual network can belong to multiple network groups with multiple connectivity configurations applied simultaneously as well. |
+| TargetResourceIds | Resource ID of the virtual network that experienced a change in connectivity configuration application. |
+| Message | A static message stating if the connectivity configuration change was successful or unsuccessful. |
+
+Within the `AppliedConnectivityConfigurations` attribute are several nested attributes:
+
+| AppliedConnectivityConfigurations attributes | Description |
+|-----------------------------|-------------|
+| ConfigurationId | ID of a connectivity configuration applied onto the virtual network. |
+| Topology | Type of topology the connectivity configuration is intended to build among the network group(s) it is applied to. Can be Mesh or HubAndSpoke. |
+
 ## Accessing logs
 
 Depending on how you consume event logs, you need to set up a Log Analytics workspace or a storage account for storing your log events. 
@@ -100,9 +135,9 @@ When setting up a Log Analytics workspace or a storage account, you need to sele
 The network manager accessing the events isn't required to be in the same subscription as the Log Analytics workspace or the storage account used for storage, but permissions may restrict your ability to access logs across different subscriptions. 
 
 > [!NOTE]
-> At least one virtual network must be added or removed from a network group in order to generate logs. A log will generate for this event a couple minutes after network group membership change occurs. 
+> At least one virtual network must experience an event captured by the categories above in order to generate logs. A log will generate for each event a couple minutes after the change occurs. 
 
 ## Next steps
-- Learn to Configure Create an [Azure Virtual Network Manager](create-virtual-network-manager-portal.md) instance using the Azure portal.
+- Learn to [get started with Azure Virtual Network Manager's event logs](how-to-configure-event-logs.md).
+- Learn to create an [Azure Virtual Network Manager](create-virtual-network-manager-portal.md) instance using the Azure Portal.
 - Learn more about [network groups](concept-network-groups.md) in Azure Virtual Network Manager.
-