From 2b96d922351c366594ca963e1a15f36ceff439a1 Mon Sep 17 00:00:00 2001 From: Microsoft Graph DevX Tooling Date: Tue, 10 Dec 2024 12:23:15 +0000 Subject: [PATCH] feat(generation): update request builders and models Update generated files with build 173698 --- .../ResourceConnectionItemRequestBuilder.php | 6 ++-- .../Item/UpdatableAssetItemRequestBuilder.php | 6 ++-- ...etItemRequestBuilderGetQueryParameters.php | 2 +- .../ComplianceChangeItemRequestBuilder.php | 12 +++---- .../Invite/InviteRequestBuilder.php | 6 ++-- .../HardwareOathDevicesRequestBuilder.php | 4 +-- ...evicesRequestBuilderGetQueryParameters.php | 2 +- .../Item/AssignTo/AssignToRequestBuilder.php | 4 +-- ...signToRequestBuilderGetQueryParameters.php | 2 +- ...ticationMethodDeviceItemRequestBuilder.php | 4 +-- ...ceItemRequestBuilderGetQueryParameters.php | 2 +- .../Invite/InviteRequestBuilder.php | 6 ++-- ...heduledActionForRuleItemRequestBuilder.php | 4 +-- ...leItemRequestBuilderGetQueryParameters.php | 2 +- .../ScheduledActionsForRuleRequestBuilder.php | 4 +-- ...orRuleRequestBuilderGetQueryParameters.php | 2 +- .../RetrieveReviewStatusRequestBuilder.php | 5 +-- .../RetrieveSnapshotsRequestBuilder.php | 5 +-- ...pshotsRequestBuilderGetQueryParameters.php | 2 +- .../SetReviewStatusRequestBuilder.php | 5 +-- ...henticationMethodDevicesRequestBuilder.php | 4 +-- ...evicesRequestBuilderGetQueryParameters.php | 2 +- .../HardwareOathDevicesRequestBuilder.php | 10 +++--- ...evicesRequestBuilderGetQueryParameters.php | 2 +- .../Item/AssignTo/AssignToRequestBuilder.php | 4 +-- ...signToRequestBuilderGetQueryParameters.php | 2 +- ...ticationMethodDeviceItemRequestBuilder.php | 15 ++++---- ...ceItemRequestBuilderGetQueryParameters.php | 2 +- .../Workbook/Tables/Add/AddRequestBuilder.php | 6 ++-- .../Item/Tables/Add/AddRequestBuilder.php | 6 ++-- .../AuthorizationSystemItemRequestBuilder.php | 4 +-- ...emItemRequestBuilderGetQueryParameters.php | 2 +- .../Item/Schema/SchemaRequestBuilder.php | 6 ++-- .../DataConnectorsRequestBuilder.php | 6 ++-- .../InboundFlowsRequestBuilder.php | 6 ++-- src/Generated/Groups/GroupsRequestBuilder.php | 6 ++-- .../Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Instances/Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Instances/Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Events/Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Instances/Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Instances/Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Instances/Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Instances/Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../ConversationsRequestBuilder.php | 6 ++-- .../Item/ConversationItemRequestBuilder.php | 12 +++---- ...onItemRequestBuilderGetQueryParameters.php | 2 +- .../Item/Reply/ReplyRequestBuilder.php | 6 ++-- .../Item/Events/Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Instances/Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Instances/Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Item/NotebookItemRequestBuilder.php | 4 +-- ...okItemRequestBuilderGetQueryParameters.php | 2 +- .../Notebooks/NotebooksRequestBuilder.php | 4 +-- ...ebooksRequestBuilderGetQueryParameters.php | 2 +- .../Item/OnenotePageItemRequestBuilder.php | 4 +-- ...geItemRequestBuilderGetQueryParameters.php | 2 +- .../Onenote/Pages/PagesRequestBuilder.php | 4 +-- .../PagesRequestBuilderGetQueryParameters.php | 2 +- .../Item/SectionGroupItemRequestBuilder.php | 4 +-- ...upItemRequestBuilderGetQueryParameters.php | 2 +- .../SectionGroupsRequestBuilder.php | 4 +-- ...GroupsRequestBuilderGetQueryParameters.php | 2 +- .../Item/OnenoteSectionItemRequestBuilder.php | 4 +-- ...onItemRequestBuilderGetQueryParameters.php | 2 +- .../Sections/SectionsRequestBuilder.php | 4 +-- ...ctionsRequestBuilderGetQueryParameters.php | 2 +- .../Item/NotebookItemRequestBuilder.php | 4 +-- ...okItemRequestBuilderGetQueryParameters.php | 2 +- .../Notebooks/NotebooksRequestBuilder.php | 4 +-- ...ebooksRequestBuilderGetQueryParameters.php | 2 +- .../Item/OnenotePageItemRequestBuilder.php | 4 +-- ...geItemRequestBuilderGetQueryParameters.php | 2 +- .../Onenote/Pages/PagesRequestBuilder.php | 4 +-- .../PagesRequestBuilderGetQueryParameters.php | 2 +- .../Item/SectionGroupItemRequestBuilder.php | 4 +-- ...upItemRequestBuilderGetQueryParameters.php | 2 +- .../SectionGroupsRequestBuilder.php | 4 +-- ...GroupsRequestBuilderGetQueryParameters.php | 2 +- .../Item/OnenoteSectionItemRequestBuilder.php | 4 +-- ...onItemRequestBuilderGetQueryParameters.php | 2 +- .../Sections/SectionsRequestBuilder.php | 4 +-- ...ctionsRequestBuilderGetQueryParameters.php | 2 +- .../Item/Reply/ReplyRequestBuilder.php | 6 ++-- .../Item/NamedLocationItemRequestBuilder.php | 6 ++-- ...stomCalloutExtensionItemRequestBuilder.php | 6 ++-- ...onItemRequestBuilderGetQueryParameters.php | 2 +- ...ageWorkflowExtensionItemRequestBuilder.php | 6 ++-- .../Item/AccessPackageItemRequestBuilder.php | 6 ++-- ...geItemRequestBuilderGetQueryParameters.php | 2 +- ...ssPackagesWithUniqueNameRequestBuilder.php | 6 ++-- ...ueNameRequestBuilderGetQueryParameters.php | 2 +- .../Item/AgreementItemRequestBuilder.php | 6 ++-- ...ntItemRequestBuilderGetQueryParameters.php | 2 +- .../Item/RiskDetectionItemRequestBuilder.php | 6 ++-- ...onItemRequestBuilderGetQueryParameters.php | 2 +- .../Models/AndroidManagedAppProtection.php | 8 ++--- src/Generated/Models/Authentication.php | 4 +-- .../Models/AuthenticationMethodDevice.php | 8 ++--- src/Generated/Models/BaseSitePage.php | 4 +-- ...udPcCrossRegionDisasterRecoverySetting.php | 8 ++--- .../Models/DeviceCompliancePolicy.php | 4 +-- ...ntConfigurationChoiceSettingDefinition.php | 8 ++--- ...onfigurationReferredSettingInformation.php | 4 +-- ...rationSettingGroupCollectionDefinition.php | 8 ++--- ...entConfigurationSettingGroupDefinition.php | 4 +-- ...ationSimpleSettingCollectionDefinition.php | 8 ++--- src/Generated/Models/Directory.php | 4 +-- .../Models/EducationalActivityDetail.php | 12 +++---- src/Generated/Models/ExpirationPattern.php | 8 ++--- .../ExternalConnectors/Configuration.php | 4 +-- .../Models/ExternalConnectors/External.php | 4 +-- .../HardwareOathAuthenticationMethod.php | 4 +-- ...areOathTokenAuthenticationMethodDevice.php | 36 +++++++++---------- src/Generated/Models/Identity.php | 8 ++--- src/Generated/Models/IdentitySet.php | 12 +++---- src/Generated/Models/Initiator.php | 4 +-- src/Generated/Models/ItemAttachment.php | 4 +-- src/Generated/Models/KeyValuePair.php | 8 ++--- .../Models/MacOsLobAppAssignmentSettings.php | 4 +-- src/Generated/Models/MailTips.php | 20 +++++------ .../Models/MailboxRestoreArtifact.php | 8 ++--- .../Models/Networkaccess/Connectivity.php | 8 ++--- .../Models/Networkaccess/Profile.php | 12 +++---- src/Generated/Models/NewsLinkPage.php | 12 +++---- ...llectionExternalUsersSelfServiceSignUp.php | 4 +-- .../OnInteractiveAuthFlowStartListener.php | 4 +-- .../OneDriveForBusinessProtectionPolicy.php | 8 ++--- .../OneDriveForBusinessRestoreSession.php | 4 +-- src/Generated/Models/Onenote.php | 16 ++++----- .../Models/RestoreSessionArtifactCount.php | 16 ++++----- src/Generated/Models/RestoreSessionBase.php | 8 ++--- .../Models/WindowsDomainJoinConfiguration.php | 4 +-- ...dowsUniversalAppXAppAssignmentSettings.php | 4 +-- .../Item/PolicyLinkItemRequestBuilder.php | 4 +-- ...nkItemRequestBuilderGetQueryParameters.php | 2 +- .../Item/Policies/PoliciesRequestBuilder.php | 4 +-- ...liciesRequestBuilderGetQueryParameters.php | 2 +- .../Item/PolicyLinkItemRequestBuilder.php | 4 +-- ...nkItemRequestBuilderGetQueryParameters.php | 2 +- .../Item/Policies/PoliciesRequestBuilder.php | 4 +-- ...liciesRequestBuilderGetQueryParameters.php | 2 +- .../Item/RemoteNetworkItemRequestBuilder.php | 4 +-- ...rkItemRequestBuilderGetQueryParameters.php | 2 +- .../RemoteNetworksRequestBuilder.php | 4 +-- ...tworksRequestBuilderGetQueryParameters.php | 2 +- .../Item/PolicyLinkItemRequestBuilder.php | 4 +-- ...nkItemRequestBuilderGetQueryParameters.php | 2 +- .../Item/Policies/PoliciesRequestBuilder.php | 4 +-- ...liciesRequestBuilderGetQueryParameters.php | 2 +- .../IdentitySynchronizationRequestBuilder.php | 6 ++-- ...tedTokenValidationPolicyRequestBuilder.php | 6 ++-- ...PolicyRequestBuilderGetQueryParameters.php | 2 +- .../RiskDetectionsRequestBuilder.php | 6 ++-- ...ctionsRequestBuilderGetQueryParameters.php | 2 +- .../ClaimsPolicyRequestBuilder.php | 12 +++---- .../Item/NotebookItemRequestBuilder.php | 4 +-- ...okItemRequestBuilderGetQueryParameters.php | 2 +- .../Notebooks/NotebooksRequestBuilder.php | 4 +-- ...ebooksRequestBuilderGetQueryParameters.php | 2 +- .../Item/OnenotePageItemRequestBuilder.php | 4 +-- ...geItemRequestBuilderGetQueryParameters.php | 2 +- .../Onenote/Pages/PagesRequestBuilder.php | 4 +-- .../PagesRequestBuilderGetQueryParameters.php | 2 +- .../Item/SectionGroupItemRequestBuilder.php | 4 +-- ...upItemRequestBuilderGetQueryParameters.php | 2 +- .../SectionGroupsRequestBuilder.php | 4 +-- ...GroupsRequestBuilderGetQueryParameters.php | 2 +- .../Item/OnenoteSectionItemRequestBuilder.php | 4 +-- ...onItemRequestBuilderGetQueryParameters.php | 2 +- .../Sections/SectionsRequestBuilder.php | 4 +-- ...ctionsRequestBuilderGetQueryParameters.php | 2 +- .../Sites/Item/Pages/PagesRequestBuilder.php | 6 ++-- .../DriveProtectionUnitItemRequestBuilder.php | 4 +-- ...itItemRequestBuilderGetQueryParameters.php | 2 +- ...DriveRestoreArtifactItemRequestBuilder.php | 4 +-- ...ctItemRequestBuilderGetQueryParameters.php | 2 +- .../Item/Messages/MessagesRequestBuilder.php | 6 ++-- .../OpenShifts/OpenShiftsRequestBuilder.php | 4 +-- ...GraphManagedTenantsApplyRequestBuilder.php | 4 +-- .../JoinRequest/JoinRequestRequestBuilder.php | 4 +-- .../MultiTenantOrganizationRequestBuilder.php | 6 ++-- .../AssignAndActivateRequestBuilder.php | 5 +-- ...ndActivateBySerialNumberRequestBuilder.php | 5 +-- .../HardwareOathMethodsRequestBuilder.php | 4 +-- ...ethodsRequestBuilderGetQueryParameters.php | 2 +- .../Item/Activate/ActivateRequestBuilder.php | 5 +-- .../Deactivate/DeactivateRequestBuilder.php | 5 +-- .../AssignTo/AssignToRequestBuilder.php | 4 +-- ...signToRequestBuilderGetQueryParameters.php | 2 +- .../Item/Device/DeviceRequestBuilder.php | 4 +-- ...DeviceRequestBuilderGetQueryParameters.php | 2 +- .../HardwareOathDevicesRequestBuilder.php | 4 +-- ...evicesRequestBuilderGetQueryParameters.php | 2 +- .../Item/AssignTo/AssignToRequestBuilder.php | 4 +-- ...signToRequestBuilderGetQueryParameters.php | 2 +- ...ticationMethodDeviceItemRequestBuilder.php | 4 +-- ...ceItemRequestBuilderGetQueryParameters.php | 2 +- ...AuthenticationMethodItemRequestBuilder.php | 4 +-- ...odItemRequestBuilderGetQueryParameters.php | 2 +- .../Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Instances/Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Instances/Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Events/Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Instances/Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Instances/Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Instances/Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Instances/Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Item/Events/Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Instances/Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Instances/Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Instances/Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Instances/Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Instances/Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Instances/Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Item/Events/Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Instances/Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Instances/Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../RetrieveReviewStatusRequestBuilder.php | 5 +-- .../RetrieveSnapshotsRequestBuilder.php | 5 +-- ...pshotsRequestBuilderGetQueryParameters.php | 2 +- .../SetReviewStatusRequestBuilder.php | 5 +-- .../Item/Events/Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Instances/Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Instances/Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Messages/Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Messages/Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Messages/Delta/DeltaRequestBuilder.php | 4 +-- .../DeltaRequestBuilderGetQueryParameters.php | 2 +- .../Item/NotebookItemRequestBuilder.php | 4 +-- ...okItemRequestBuilderGetQueryParameters.php | 2 +- .../Notebooks/NotebooksRequestBuilder.php | 4 +-- ...ebooksRequestBuilderGetQueryParameters.php | 2 +- .../Item/OnenotePageItemRequestBuilder.php | 4 +-- ...geItemRequestBuilderGetQueryParameters.php | 2 +- .../Onenote/Pages/PagesRequestBuilder.php | 4 +-- .../PagesRequestBuilderGetQueryParameters.php | 2 +- .../Item/SectionGroupItemRequestBuilder.php | 4 +-- ...upItemRequestBuilderGetQueryParameters.php | 2 +- .../SectionGroupsRequestBuilder.php | 4 +-- ...GroupsRequestBuilderGetQueryParameters.php | 2 +- .../Item/OnenoteSectionItemRequestBuilder.php | 4 +-- ...onItemRequestBuilderGetQueryParameters.php | 2 +- .../Sections/SectionsRequestBuilder.php | 4 +-- ...ctionsRequestBuilderGetQueryParameters.php | 2 +- .../Item/Presence/PresenceRequestBuilder.php | 6 ++-- ...esenceRequestBuilderGetQueryParameters.php | 2 +- src/Generated/kiota-lock.json | 4 +-- 338 files changed, 680 insertions(+), 665 deletions(-) diff --git a/src/Generated/Admin/Windows/Updates/ResourceConnections/Item/ResourceConnectionItemRequestBuilder.php b/src/Generated/Admin/Windows/Updates/ResourceConnections/Item/ResourceConnectionItemRequestBuilder.php index 441a0011a6c..0963fa28217 100644 --- a/src/Generated/Admin/Windows/Updates/ResourceConnections/Item/ResourceConnectionItemRequestBuilder.php +++ b/src/Generated/Admin/Windows/Updates/ResourceConnections/Item/ResourceConnectionItemRequestBuilder.php @@ -31,11 +31,11 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Delete an operationalInsightsConnection object. + * Delete a resourceConnection object. * @param ResourceConnectionItemRequestBuilderDeleteRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception - * @link https://learn.microsoft.com/graph/api/windowsupdates-operationalinsightsconnection-delete?view=graph-rest-beta Find more info here + * @link https://learn.microsoft.com/graph/api/windowsupdates-resourceconnection-delete?view=graph-rest-beta Find more info here */ public function delete(?ResourceConnectionItemRequestBuilderDeleteRequestConfiguration $requestConfiguration = null): Promise { $requestInfo = $this->toDeleteRequestInformation($requestConfiguration); @@ -76,7 +76,7 @@ public function patch(ResourceConnection $body, ?ResourceConnectionItemRequestBu } /** - * Delete an operationalInsightsConnection object. + * Delete a resourceConnection object. * @param ResourceConnectionItemRequestBuilderDeleteRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Admin/Windows/Updates/UpdatableAssets/Item/UpdatableAssetItemRequestBuilder.php b/src/Generated/Admin/Windows/Updates/UpdatableAssets/Item/UpdatableAssetItemRequestBuilder.php index f481ba30a96..a340ff11b06 100644 --- a/src/Generated/Admin/Windows/Updates/UpdatableAssets/Item/UpdatableAssetItemRequestBuilder.php +++ b/src/Generated/Admin/Windows/Updates/UpdatableAssets/Item/UpdatableAssetItemRequestBuilder.php @@ -78,11 +78,11 @@ public function delete(?UpdatableAssetItemRequestBuilderDeleteRequestConfigurati } /** - * Read the properties and relationships of an updatableAssetGroup object. + * Read the properties and relationships of an updatableAsset object. * @param UpdatableAssetItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception - * @link https://learn.microsoft.com/graph/api/windowsupdates-updatableassetgroup-get?view=graph-rest-beta Find more info here + * @link https://learn.microsoft.com/graph/api/windowsupdates-updatableasset-get?view=graph-rest-beta Find more info here */ public function get(?UpdatableAssetItemRequestBuilderGetRequestConfiguration $requestConfiguration = null): Promise { $requestInfo = $this->toGetRequestInformation($requestConfiguration); @@ -126,7 +126,7 @@ public function toDeleteRequestInformation(?UpdatableAssetItemRequestBuilderDele } /** - * Read the properties and relationships of an updatableAssetGroup object. + * Read the properties and relationships of an updatableAsset object. * @param UpdatableAssetItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Admin/Windows/Updates/UpdatableAssets/Item/UpdatableAssetItemRequestBuilderGetQueryParameters.php b/src/Generated/Admin/Windows/Updates/UpdatableAssets/Item/UpdatableAssetItemRequestBuilderGetQueryParameters.php index 1572dffe84e..e3e97b05f38 100644 --- a/src/Generated/Admin/Windows/Updates/UpdatableAssets/Item/UpdatableAssetItemRequestBuilderGetQueryParameters.php +++ b/src/Generated/Admin/Windows/Updates/UpdatableAssets/Item/UpdatableAssetItemRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Read the properties and relationships of an updatableAssetGroup object. + * Read the properties and relationships of an updatableAsset object. */ class UpdatableAssetItemRequestBuilderGetQueryParameters { diff --git a/src/Generated/Admin/Windows/Updates/UpdatePolicies/Item/ComplianceChanges/Item/ComplianceChangeItemRequestBuilder.php b/src/Generated/Admin/Windows/Updates/UpdatePolicies/Item/ComplianceChanges/Item/ComplianceChangeItemRequestBuilder.php index bcbb5d39e92..0e69dd4166f 100644 --- a/src/Generated/Admin/Windows/Updates/UpdatePolicies/Item/ComplianceChanges/Item/ComplianceChangeItemRequestBuilder.php +++ b/src/Generated/Admin/Windows/Updates/UpdatePolicies/Item/ComplianceChanges/Item/ComplianceChangeItemRequestBuilder.php @@ -39,11 +39,11 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Delete a complianceChange object. + * Delete a contentApproval object. * @param ComplianceChangeItemRequestBuilderDeleteRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception - * @link https://learn.microsoft.com/graph/api/windowsupdates-compliancechange-delete?view=graph-rest-beta Find more info here + * @link https://learn.microsoft.com/graph/api/windowsupdates-contentapproval-delete?view=graph-rest-beta Find more info here */ public function delete(?ComplianceChangeItemRequestBuilderDeleteRequestConfiguration $requestConfiguration = null): Promise { $requestInfo = $this->toDeleteRequestInformation($requestConfiguration); @@ -69,12 +69,12 @@ public function get(?ComplianceChangeItemRequestBuilderGetRequestConfiguration $ } /** - * Update the properties of a complianceChange object. + * Update the properties of a contentApproval object. * @param ComplianceChange $body The request body * @param ComplianceChangeItemRequestBuilderPatchRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception - * @link https://learn.microsoft.com/graph/api/windowsupdates-compliancechange-update?view=graph-rest-beta Find more info here + * @link https://learn.microsoft.com/graph/api/windowsupdates-contentapproval-update?view=graph-rest-beta Find more info here */ public function patch(ComplianceChange $body, ?ComplianceChangeItemRequestBuilderPatchRequestConfiguration $requestConfiguration = null): Promise { $requestInfo = $this->toPatchRequestInformation($body, $requestConfiguration); @@ -85,7 +85,7 @@ public function patch(ComplianceChange $body, ?ComplianceChangeItemRequestBuilde } /** - * Delete a complianceChange object. + * Delete a contentApproval object. * @param ComplianceChangeItemRequestBuilderDeleteRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ @@ -124,7 +124,7 @@ public function toGetRequestInformation(?ComplianceChangeItemRequestBuilderGetRe } /** - * Update the properties of a complianceChange object. + * Update the properties of a contentApproval object. * @param ComplianceChange $body The request body * @param ComplianceChangeItemRequestBuilderPatchRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation diff --git a/src/Generated/App/Calls/Item/Participants/Invite/InviteRequestBuilder.php b/src/Generated/App/Calls/Item/Participants/Invite/InviteRequestBuilder.php index 94bd9218eff..0f05c8b184a 100644 --- a/src/Generated/App/Calls/Item/Participants/Invite/InviteRequestBuilder.php +++ b/src/Generated/App/Calls/Item/Participants/Invite/InviteRequestBuilder.php @@ -31,12 +31,12 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Invite participants to the active call. For more information about how to handle operations, see commsOperation. + * Delete a specific participant in a call. In some situations, it is appropriate for an application to remove a participant from an active call. This action can be done before or after the participant answers the call. When an active caller is removed, they are immediately dropped from the call with no pre- or post-removal notification. When an invited participant is removed, any outstanding add participant request is canceled. * @param InvitePostRequestBody $body The request body * @param InviteRequestBuilderPostRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception - * @link https://learn.microsoft.com/graph/api/participant-invite?view=graph-rest-beta Find more info here + * @link https://learn.microsoft.com/graph/api/participant-delete?view=graph-rest-beta Find more info here */ public function post(InvitePostRequestBody $body, ?InviteRequestBuilderPostRequestConfiguration $requestConfiguration = null): Promise { $requestInfo = $this->toPostRequestInformation($body, $requestConfiguration); @@ -47,7 +47,7 @@ public function post(InvitePostRequestBody $body, ?InviteRequestBuilderPostReque } /** - * Invite participants to the active call. For more information about how to handle operations, see commsOperation. + * Delete a specific participant in a call. In some situations, it is appropriate for an application to remove a participant from an active call. This action can be done before or after the participant answers the call. When an active caller is removed, they are immediately dropped from the call with no pre- or post-removal notification. When an invited participant is removed, any outstanding add participant request is canceled. * @param InvitePostRequestBody $body The request body * @param InviteRequestBuilderPostRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation diff --git a/src/Generated/AuthenticationMethodDevices/Item/HardwareOathDevices/HardwareOathDevicesRequestBuilder.php b/src/Generated/AuthenticationMethodDevices/Item/HardwareOathDevices/HardwareOathDevicesRequestBuilder.php index 79f6bafcec2..d536c726c1c 100644 --- a/src/Generated/AuthenticationMethodDevices/Item/HardwareOathDevices/HardwareOathDevicesRequestBuilder.php +++ b/src/Generated/AuthenticationMethodDevices/Item/HardwareOathDevices/HardwareOathDevicesRequestBuilder.php @@ -52,7 +52,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get hardwareOathDevices from authenticationMethodDevices + * Exposes the hardware OATH method in the directory. * @param HardwareOathDevicesRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -81,7 +81,7 @@ public function post(HardwareOathTokenAuthenticationMethodDevice $body, ?Hardwar } /** - * Get hardwareOathDevices from authenticationMethodDevices + * Exposes the hardware OATH method in the directory. * @param HardwareOathDevicesRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/AuthenticationMethodDevices/Item/HardwareOathDevices/HardwareOathDevicesRequestBuilderGetQueryParameters.php b/src/Generated/AuthenticationMethodDevices/Item/HardwareOathDevices/HardwareOathDevicesRequestBuilderGetQueryParameters.php index b26627f072a..ed02e1c1a88 100644 --- a/src/Generated/AuthenticationMethodDevices/Item/HardwareOathDevices/HardwareOathDevicesRequestBuilderGetQueryParameters.php +++ b/src/Generated/AuthenticationMethodDevices/Item/HardwareOathDevices/HardwareOathDevicesRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get hardwareOathDevices from authenticationMethodDevices + * Exposes the hardware OATH method in the directory. */ class HardwareOathDevicesRequestBuilderGetQueryParameters { diff --git a/src/Generated/AuthenticationMethodDevices/Item/HardwareOathDevices/Item/AssignTo/AssignToRequestBuilder.php b/src/Generated/AuthenticationMethodDevices/Item/HardwareOathDevices/Item/AssignTo/AssignToRequestBuilder.php index e428b5295d1..0ea1284b9ba 100644 --- a/src/Generated/AuthenticationMethodDevices/Item/HardwareOathDevices/Item/AssignTo/AssignToRequestBuilder.php +++ b/src/Generated/AuthenticationMethodDevices/Item/HardwareOathDevices/Item/AssignTo/AssignToRequestBuilder.php @@ -47,7 +47,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get assignTo from authenticationMethodDevices + * Assign the hardware OATH token to a user. * @param AssignToRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -61,7 +61,7 @@ public function get(?AssignToRequestBuilderGetRequestConfiguration $requestConfi } /** - * Get assignTo from authenticationMethodDevices + * Assign the hardware OATH token to a user. * @param AssignToRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/AuthenticationMethodDevices/Item/HardwareOathDevices/Item/AssignTo/AssignToRequestBuilderGetQueryParameters.php b/src/Generated/AuthenticationMethodDevices/Item/HardwareOathDevices/Item/AssignTo/AssignToRequestBuilderGetQueryParameters.php index 790a95efe0e..0e0e6e309ac 100644 --- a/src/Generated/AuthenticationMethodDevices/Item/HardwareOathDevices/Item/AssignTo/AssignToRequestBuilderGetQueryParameters.php +++ b/src/Generated/AuthenticationMethodDevices/Item/HardwareOathDevices/Item/AssignTo/AssignToRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get assignTo from authenticationMethodDevices + * Assign the hardware OATH token to a user. */ class AssignToRequestBuilderGetQueryParameters { diff --git a/src/Generated/AuthenticationMethodDevices/Item/HardwareOathDevices/Item/HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilder.php b/src/Generated/AuthenticationMethodDevices/Item/HardwareOathDevices/Item/HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilder.php index 6183fd5db26..e19b4ed05b4 100644 --- a/src/Generated/AuthenticationMethodDevices/Item/HardwareOathDevices/Item/HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilder.php +++ b/src/Generated/AuthenticationMethodDevices/Item/HardwareOathDevices/Item/HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilder.php @@ -53,7 +53,7 @@ public function delete(?HardwareOathTokenAuthenticationMethodDeviceItemRequestBu } /** - * Get hardwareOathDevices from authenticationMethodDevices + * Exposes the hardware OATH method in the directory. * @param HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -100,7 +100,7 @@ public function toDeleteRequestInformation(?HardwareOathTokenAuthenticationMetho } /** - * Get hardwareOathDevices from authenticationMethodDevices + * Exposes the hardware OATH method in the directory. * @param HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/AuthenticationMethodDevices/Item/HardwareOathDevices/Item/HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilderGetQueryParameters.php b/src/Generated/AuthenticationMethodDevices/Item/HardwareOathDevices/Item/HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilderGetQueryParameters.php index 0ca4b2e371d..01502da718e 100644 --- a/src/Generated/AuthenticationMethodDevices/Item/HardwareOathDevices/Item/HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilderGetQueryParameters.php +++ b/src/Generated/AuthenticationMethodDevices/Item/HardwareOathDevices/Item/HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get hardwareOathDevices from authenticationMethodDevices + * Exposes the hardware OATH method in the directory. */ class HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilderGetQueryParameters { diff --git a/src/Generated/Communications/Calls/Item/Participants/Invite/InviteRequestBuilder.php b/src/Generated/Communications/Calls/Item/Participants/Invite/InviteRequestBuilder.php index 99a9667d827..e48dfa18977 100644 --- a/src/Generated/Communications/Calls/Item/Participants/Invite/InviteRequestBuilder.php +++ b/src/Generated/Communications/Calls/Item/Participants/Invite/InviteRequestBuilder.php @@ -31,12 +31,12 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Invite participants to the active call. For more information about how to handle operations, see commsOperation. + * Delete a specific participant in a call. In some situations, it is appropriate for an application to remove a participant from an active call. This action can be done before or after the participant answers the call. When an active caller is removed, they are immediately dropped from the call with no pre- or post-removal notification. When an invited participant is removed, any outstanding add participant request is canceled. * @param InvitePostRequestBody $body The request body * @param InviteRequestBuilderPostRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception - * @link https://learn.microsoft.com/graph/api/participant-invite?view=graph-rest-beta Find more info here + * @link https://learn.microsoft.com/graph/api/participant-delete?view=graph-rest-beta Find more info here */ public function post(InvitePostRequestBody $body, ?InviteRequestBuilderPostRequestConfiguration $requestConfiguration = null): Promise { $requestInfo = $this->toPostRequestInformation($body, $requestConfiguration); @@ -47,7 +47,7 @@ public function post(InvitePostRequestBody $body, ?InviteRequestBuilderPostReque } /** - * Invite participants to the active call. For more information about how to handle operations, see commsOperation. + * Delete a specific participant in a call. In some situations, it is appropriate for an application to remove a participant from an active call. This action can be done before or after the participant answers the call. When an active caller is removed, they are immediately dropped from the call with no pre- or post-removal notification. When an invited participant is removed, any outstanding add participant request is canceled. * @param InvitePostRequestBody $body The request body * @param InviteRequestBuilderPostRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation diff --git a/src/Generated/DeviceManagement/DeviceCompliancePolicies/Item/ScheduledActionsForRule/Item/DeviceComplianceScheduledActionForRuleItemRequestBuilder.php b/src/Generated/DeviceManagement/DeviceCompliancePolicies/Item/ScheduledActionsForRule/Item/DeviceComplianceScheduledActionForRuleItemRequestBuilder.php index b80e5d79ed8..a145ae633ab 100644 --- a/src/Generated/DeviceManagement/DeviceCompliancePolicies/Item/ScheduledActionsForRule/Item/DeviceComplianceScheduledActionForRuleItemRequestBuilder.php +++ b/src/Generated/DeviceManagement/DeviceCompliancePolicies/Item/ScheduledActionsForRule/Item/DeviceComplianceScheduledActionForRuleItemRequestBuilder.php @@ -53,7 +53,7 @@ public function delete(?DeviceComplianceScheduledActionForRuleItemRequestBuilder } /** - * The list of scheduled action for this rule + * The list of scheduled action per rule for this compliance policy. This is a required property when creating any individual per-platform compliance policies. * @param DeviceComplianceScheduledActionForRuleItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -100,7 +100,7 @@ public function toDeleteRequestInformation(?DeviceComplianceScheduledActionForRu } /** - * The list of scheduled action for this rule + * The list of scheduled action per rule for this compliance policy. This is a required property when creating any individual per-platform compliance policies. * @param DeviceComplianceScheduledActionForRuleItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/DeviceManagement/DeviceCompliancePolicies/Item/ScheduledActionsForRule/Item/DeviceComplianceScheduledActionForRuleItemRequestBuilderGetQueryParameters.php b/src/Generated/DeviceManagement/DeviceCompliancePolicies/Item/ScheduledActionsForRule/Item/DeviceComplianceScheduledActionForRuleItemRequestBuilderGetQueryParameters.php index 0f745123334..253415c5c8d 100644 --- a/src/Generated/DeviceManagement/DeviceCompliancePolicies/Item/ScheduledActionsForRule/Item/DeviceComplianceScheduledActionForRuleItemRequestBuilderGetQueryParameters.php +++ b/src/Generated/DeviceManagement/DeviceCompliancePolicies/Item/ScheduledActionsForRule/Item/DeviceComplianceScheduledActionForRuleItemRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * The list of scheduled action for this rule + * The list of scheduled action per rule for this compliance policy. This is a required property when creating any individual per-platform compliance policies. */ class DeviceComplianceScheduledActionForRuleItemRequestBuilderGetQueryParameters { diff --git a/src/Generated/DeviceManagement/DeviceCompliancePolicies/Item/ScheduledActionsForRule/ScheduledActionsForRuleRequestBuilder.php b/src/Generated/DeviceManagement/DeviceCompliancePolicies/Item/ScheduledActionsForRule/ScheduledActionsForRuleRequestBuilder.php index bb4f67a3ce3..a85baf0f7f7 100644 --- a/src/Generated/DeviceManagement/DeviceCompliancePolicies/Item/ScheduledActionsForRule/ScheduledActionsForRuleRequestBuilder.php +++ b/src/Generated/DeviceManagement/DeviceCompliancePolicies/Item/ScheduledActionsForRule/ScheduledActionsForRuleRequestBuilder.php @@ -52,7 +52,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * The list of scheduled action for this rule + * The list of scheduled action per rule for this compliance policy. This is a required property when creating any individual per-platform compliance policies. * @param ScheduledActionsForRuleRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -81,7 +81,7 @@ public function post(DeviceComplianceScheduledActionForRule $body, ?ScheduledAct } /** - * The list of scheduled action for this rule + * The list of scheduled action per rule for this compliance policy. This is a required property when creating any individual per-platform compliance policies. * @param ScheduledActionsForRuleRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/DeviceManagement/DeviceCompliancePolicies/Item/ScheduledActionsForRule/ScheduledActionsForRuleRequestBuilderGetQueryParameters.php b/src/Generated/DeviceManagement/DeviceCompliancePolicies/Item/ScheduledActionsForRule/ScheduledActionsForRuleRequestBuilderGetQueryParameters.php index 614c634523d..4ffc159cb20 100644 --- a/src/Generated/DeviceManagement/DeviceCompliancePolicies/Item/ScheduledActionsForRule/ScheduledActionsForRuleRequestBuilderGetQueryParameters.php +++ b/src/Generated/DeviceManagement/DeviceCompliancePolicies/Item/ScheduledActionsForRule/ScheduledActionsForRuleRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * The list of scheduled action for this rule + * The list of scheduled action per rule for this compliance policy. This is a required property when creating any individual per-platform compliance policies. */ class ScheduledActionsForRuleRequestBuilderGetQueryParameters { diff --git a/src/Generated/DeviceManagement/VirtualEndpoint/CloudPCs/Item/RetrieveReviewStatus/RetrieveReviewStatusRequestBuilder.php b/src/Generated/DeviceManagement/VirtualEndpoint/CloudPCs/Item/RetrieveReviewStatus/RetrieveReviewStatusRequestBuilder.php index 3f1f763e93a..dead3e061c2 100644 --- a/src/Generated/DeviceManagement/VirtualEndpoint/CloudPCs/Item/RetrieveReviewStatus/RetrieveReviewStatusRequestBuilder.php +++ b/src/Generated/DeviceManagement/VirtualEndpoint/CloudPCs/Item/RetrieveReviewStatus/RetrieveReviewStatusRequestBuilder.php @@ -31,10 +31,11 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Invoke function retrieveReviewStatus + * Get the review status of a Cloud PC. * @param RetrieveReviewStatusRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception + * @link https://learn.microsoft.com/graph/api/cloudpc-retrievereviewstatus?view=graph-rest-beta Find more info here */ public function get(?RetrieveReviewStatusRequestBuilderGetRequestConfiguration $requestConfiguration = null): Promise { $requestInfo = $this->toGetRequestInformation($requestConfiguration); @@ -45,7 +46,7 @@ public function get(?RetrieveReviewStatusRequestBuilderGetRequestConfiguration $ } /** - * Invoke function retrieveReviewStatus + * Get the review status of a Cloud PC. * @param RetrieveReviewStatusRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/DeviceManagement/VirtualEndpoint/CloudPCs/Item/RetrieveSnapshots/RetrieveSnapshotsRequestBuilder.php b/src/Generated/DeviceManagement/VirtualEndpoint/CloudPCs/Item/RetrieveSnapshots/RetrieveSnapshotsRequestBuilder.php index f679b0fe3da..0540c00d8da 100644 --- a/src/Generated/DeviceManagement/VirtualEndpoint/CloudPCs/Item/RetrieveSnapshots/RetrieveSnapshotsRequestBuilder.php +++ b/src/Generated/DeviceManagement/VirtualEndpoint/CloudPCs/Item/RetrieveSnapshots/RetrieveSnapshotsRequestBuilder.php @@ -30,10 +30,11 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Invoke function retrieveSnapshots + * List all cloudPcSnapshot resources for a Cloud PC. * @param RetrieveSnapshotsRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception + * @link https://learn.microsoft.com/graph/api/cloudpc-retrievesnapshots?view=graph-rest-beta Find more info here */ public function get(?RetrieveSnapshotsRequestBuilderGetRequestConfiguration $requestConfiguration = null): Promise { $requestInfo = $this->toGetRequestInformation($requestConfiguration); @@ -44,7 +45,7 @@ public function get(?RetrieveSnapshotsRequestBuilderGetRequestConfiguration $req } /** - * Invoke function retrieveSnapshots + * List all cloudPcSnapshot resources for a Cloud PC. * @param RetrieveSnapshotsRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/DeviceManagement/VirtualEndpoint/CloudPCs/Item/RetrieveSnapshots/RetrieveSnapshotsRequestBuilderGetQueryParameters.php b/src/Generated/DeviceManagement/VirtualEndpoint/CloudPCs/Item/RetrieveSnapshots/RetrieveSnapshotsRequestBuilderGetQueryParameters.php index 96a6de1b0b1..efee2243d62 100644 --- a/src/Generated/DeviceManagement/VirtualEndpoint/CloudPCs/Item/RetrieveSnapshots/RetrieveSnapshotsRequestBuilderGetQueryParameters.php +++ b/src/Generated/DeviceManagement/VirtualEndpoint/CloudPCs/Item/RetrieveSnapshots/RetrieveSnapshotsRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Invoke function retrieveSnapshots + * List all cloudPcSnapshot resources for a Cloud PC. */ class RetrieveSnapshotsRequestBuilderGetQueryParameters { diff --git a/src/Generated/DeviceManagement/VirtualEndpoint/CloudPCs/Item/SetReviewStatus/SetReviewStatusRequestBuilder.php b/src/Generated/DeviceManagement/VirtualEndpoint/CloudPCs/Item/SetReviewStatus/SetReviewStatusRequestBuilder.php index 44417e7b2ed..12601b85e86 100644 --- a/src/Generated/DeviceManagement/VirtualEndpoint/CloudPCs/Item/SetReviewStatus/SetReviewStatusRequestBuilder.php +++ b/src/Generated/DeviceManagement/VirtualEndpoint/CloudPCs/Item/SetReviewStatus/SetReviewStatusRequestBuilder.php @@ -30,11 +30,12 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Invoke action setReviewStatus + * Set the review status of a specific Cloud PC device using the Cloud PC ID. Use this API to set the review status of a Cloud PC to in review if you consider a Cloud PC suspicious. After the review is completed, use this API again to set the Cloud PC back to a normal state. * @param SetReviewStatusPostRequestBody $body The request body * @param SetReviewStatusRequestBuilderPostRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception + * @link https://learn.microsoft.com/graph/api/cloudpc-setreviewstatus?view=graph-rest-beta Find more info here */ public function post(SetReviewStatusPostRequestBody $body, ?SetReviewStatusRequestBuilderPostRequestConfiguration $requestConfiguration = null): Promise { $requestInfo = $this->toPostRequestInformation($body, $requestConfiguration); @@ -45,7 +46,7 @@ public function post(SetReviewStatusPostRequestBody $body, ?SetReviewStatusReque } /** - * Invoke action setReviewStatus + * Set the review status of a specific Cloud PC device using the Cloud PC ID. Use this API to set the review status of a Cloud PC to in review if you consider a Cloud PC suspicious. After the review is completed, use this API again to set the Cloud PC back to a normal state. * @param SetReviewStatusPostRequestBody $body The request body * @param SetReviewStatusRequestBuilderPostRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation diff --git a/src/Generated/Directory/AuthenticationMethodDevices/AuthenticationMethodDevicesRequestBuilder.php b/src/Generated/Directory/AuthenticationMethodDevices/AuthenticationMethodDevicesRequestBuilder.php index 24acf78a03a..332ce44882b 100644 --- a/src/Generated/Directory/AuthenticationMethodDevices/AuthenticationMethodDevicesRequestBuilder.php +++ b/src/Generated/Directory/AuthenticationMethodDevices/AuthenticationMethodDevicesRequestBuilder.php @@ -53,7 +53,7 @@ public function delete(?AuthenticationMethodDevicesRequestBuilderDeleteRequestCo } /** - * Get authenticationMethodDevices from directory + * Exposes the hardware OATH method in the directory. * @param AuthenticationMethodDevicesRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -100,7 +100,7 @@ public function toDeleteRequestInformation(?AuthenticationMethodDevicesRequestBu } /** - * Get authenticationMethodDevices from directory + * Exposes the hardware OATH method in the directory. * @param AuthenticationMethodDevicesRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Directory/AuthenticationMethodDevices/AuthenticationMethodDevicesRequestBuilderGetQueryParameters.php b/src/Generated/Directory/AuthenticationMethodDevices/AuthenticationMethodDevicesRequestBuilderGetQueryParameters.php index b128ace2455..ea0ccbdb54d 100644 --- a/src/Generated/Directory/AuthenticationMethodDevices/AuthenticationMethodDevicesRequestBuilderGetQueryParameters.php +++ b/src/Generated/Directory/AuthenticationMethodDevices/AuthenticationMethodDevicesRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get authenticationMethodDevices from directory + * Exposes the hardware OATH method in the directory. */ class AuthenticationMethodDevicesRequestBuilderGetQueryParameters { diff --git a/src/Generated/Directory/AuthenticationMethodDevices/HardwareOathDevices/HardwareOathDevicesRequestBuilder.php b/src/Generated/Directory/AuthenticationMethodDevices/HardwareOathDevices/HardwareOathDevicesRequestBuilder.php index e0825b4fc36..1dd216be38b 100644 --- a/src/Generated/Directory/AuthenticationMethodDevices/HardwareOathDevices/HardwareOathDevicesRequestBuilder.php +++ b/src/Generated/Directory/AuthenticationMethodDevices/HardwareOathDevices/HardwareOathDevicesRequestBuilder.php @@ -52,10 +52,11 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get hardwareOathDevices from directory + * List all hardware OATH tokens in the directory. * @param HardwareOathDevicesRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception + * @link https://learn.microsoft.com/graph/api/authenticationmethoddevice-list-hardwareoathdevices?view=graph-rest-beta Find more info here */ public function get(?HardwareOathDevicesRequestBuilderGetRequestConfiguration $requestConfiguration = null): Promise { $requestInfo = $this->toGetRequestInformation($requestConfiguration); @@ -66,11 +67,12 @@ public function get(?HardwareOathDevicesRequestBuilderGetRequestConfiguration $r } /** - * Create new navigation property to hardwareOathDevices for directory + * Create a new hardwareOathTokenAuthenticationMethodDevice object. Supports bulk creation. * @param HardwareOathTokenAuthenticationMethodDevice $body The request body * @param HardwareOathDevicesRequestBuilderPostRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception + * @link https://learn.microsoft.com/graph/api/authenticationmethoddevice-update?view=graph-rest-beta Find more info here */ public function post(HardwareOathTokenAuthenticationMethodDevice $body, ?HardwareOathDevicesRequestBuilderPostRequestConfiguration $requestConfiguration = null): Promise { $requestInfo = $this->toPostRequestInformation($body, $requestConfiguration); @@ -81,7 +83,7 @@ public function post(HardwareOathTokenAuthenticationMethodDevice $body, ?Hardwar } /** - * Get hardwareOathDevices from directory + * List all hardware OATH tokens in the directory. * @param HardwareOathDevicesRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ @@ -102,7 +104,7 @@ public function toGetRequestInformation(?HardwareOathDevicesRequestBuilderGetReq } /** - * Create new navigation property to hardwareOathDevices for directory + * Create a new hardwareOathTokenAuthenticationMethodDevice object. Supports bulk creation. * @param HardwareOathTokenAuthenticationMethodDevice $body The request body * @param HardwareOathDevicesRequestBuilderPostRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation diff --git a/src/Generated/Directory/AuthenticationMethodDevices/HardwareOathDevices/HardwareOathDevicesRequestBuilderGetQueryParameters.php b/src/Generated/Directory/AuthenticationMethodDevices/HardwareOathDevices/HardwareOathDevicesRequestBuilderGetQueryParameters.php index 5c57c83c746..43fee96745e 100644 --- a/src/Generated/Directory/AuthenticationMethodDevices/HardwareOathDevices/HardwareOathDevicesRequestBuilderGetQueryParameters.php +++ b/src/Generated/Directory/AuthenticationMethodDevices/HardwareOathDevices/HardwareOathDevicesRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get hardwareOathDevices from directory + * List all hardware OATH tokens in the directory. */ class HardwareOathDevicesRequestBuilderGetQueryParameters { diff --git a/src/Generated/Directory/AuthenticationMethodDevices/HardwareOathDevices/Item/AssignTo/AssignToRequestBuilder.php b/src/Generated/Directory/AuthenticationMethodDevices/HardwareOathDevices/Item/AssignTo/AssignToRequestBuilder.php index bb7fa83cd93..98a16ddf46a 100644 --- a/src/Generated/Directory/AuthenticationMethodDevices/HardwareOathDevices/Item/AssignTo/AssignToRequestBuilder.php +++ b/src/Generated/Directory/AuthenticationMethodDevices/HardwareOathDevices/Item/AssignTo/AssignToRequestBuilder.php @@ -47,7 +47,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get assignTo from directory + * Assign the hardware OATH token to a user. * @param AssignToRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -61,7 +61,7 @@ public function get(?AssignToRequestBuilderGetRequestConfiguration $requestConfi } /** - * Get assignTo from directory + * Assign the hardware OATH token to a user. * @param AssignToRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Directory/AuthenticationMethodDevices/HardwareOathDevices/Item/AssignTo/AssignToRequestBuilderGetQueryParameters.php b/src/Generated/Directory/AuthenticationMethodDevices/HardwareOathDevices/Item/AssignTo/AssignToRequestBuilderGetQueryParameters.php index 79ffd9c1a3c..e923ec827cd 100644 --- a/src/Generated/Directory/AuthenticationMethodDevices/HardwareOathDevices/Item/AssignTo/AssignToRequestBuilderGetQueryParameters.php +++ b/src/Generated/Directory/AuthenticationMethodDevices/HardwareOathDevices/Item/AssignTo/AssignToRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get assignTo from directory + * Assign the hardware OATH token to a user. */ class AssignToRequestBuilderGetQueryParameters { diff --git a/src/Generated/Directory/AuthenticationMethodDevices/HardwareOathDevices/Item/HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilder.php b/src/Generated/Directory/AuthenticationMethodDevices/HardwareOathDevices/Item/HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilder.php index b7db5b37666..6e2bca5e434 100644 --- a/src/Generated/Directory/AuthenticationMethodDevices/HardwareOathDevices/Item/HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilder.php +++ b/src/Generated/Directory/AuthenticationMethodDevices/HardwareOathDevices/Item/HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilder.php @@ -39,10 +39,11 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Delete navigation property hardwareOathDevices for directory + * Delete a Hardware OATH token. Token needs to be unassigned. * @param HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilderDeleteRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception + * @link https://learn.microsoft.com/graph/api/authenticationmethoddevice-delete-hardwareoathdevices?view=graph-rest-beta Find more info here */ public function delete(?HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilderDeleteRequestConfiguration $requestConfiguration = null): Promise { $requestInfo = $this->toDeleteRequestInformation($requestConfiguration); @@ -53,10 +54,11 @@ public function delete(?HardwareOathTokenAuthenticationMethodDeviceItemRequestBu } /** - * Get hardwareOathDevices from directory + * Read the properties and relationships of a hardwareOathTokenAuthenticationMethodDevice object. * @param HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception + * @link https://learn.microsoft.com/graph/api/hardwareoathtokenauthenticationmethoddevice-get?view=graph-rest-beta Find more info here */ public function get(?HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilderGetRequestConfiguration $requestConfiguration = null): Promise { $requestInfo = $this->toGetRequestInformation($requestConfiguration); @@ -67,11 +69,12 @@ public function get(?HardwareOathTokenAuthenticationMethodDeviceItemRequestBuild } /** - * Update the navigation property hardwareOathDevices in directory + * Update the properties of a hardwareOathTokenAuthenticationMethodDevice object. The token needs to unassigned. * @param HardwareOathTokenAuthenticationMethodDevice $body The request body * @param HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilderPatchRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception + * @link https://learn.microsoft.com/graph/api/hardwareoathtokenauthenticationmethoddevice-update?view=graph-rest-beta Find more info here */ public function patch(HardwareOathTokenAuthenticationMethodDevice $body, ?HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilderPatchRequestConfiguration $requestConfiguration = null): Promise { $requestInfo = $this->toPatchRequestInformation($body, $requestConfiguration); @@ -82,7 +85,7 @@ public function patch(HardwareOathTokenAuthenticationMethodDevice $body, ?Hardwa } /** - * Delete navigation property hardwareOathDevices for directory + * Delete a Hardware OATH token. Token needs to be unassigned. * @param HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilderDeleteRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ @@ -100,7 +103,7 @@ public function toDeleteRequestInformation(?HardwareOathTokenAuthenticationMetho } /** - * Get hardwareOathDevices from directory + * Read the properties and relationships of a hardwareOathTokenAuthenticationMethodDevice object. * @param HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ @@ -121,7 +124,7 @@ public function toGetRequestInformation(?HardwareOathTokenAuthenticationMethodDe } /** - * Update the navigation property hardwareOathDevices in directory + * Update the properties of a hardwareOathTokenAuthenticationMethodDevice object. The token needs to unassigned. * @param HardwareOathTokenAuthenticationMethodDevice $body The request body * @param HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilderPatchRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation diff --git a/src/Generated/Directory/AuthenticationMethodDevices/HardwareOathDevices/Item/HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilderGetQueryParameters.php b/src/Generated/Directory/AuthenticationMethodDevices/HardwareOathDevices/Item/HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilderGetQueryParameters.php index 5ea7a3c6ec3..6f922bfb7b0 100644 --- a/src/Generated/Directory/AuthenticationMethodDevices/HardwareOathDevices/Item/HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilderGetQueryParameters.php +++ b/src/Generated/Directory/AuthenticationMethodDevices/HardwareOathDevices/Item/HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get hardwareOathDevices from directory + * Read the properties and relationships of a hardwareOathTokenAuthenticationMethodDevice object. */ class HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilderGetQueryParameters { diff --git a/src/Generated/Drives/Item/Items/Item/Workbook/Tables/Add/AddRequestBuilder.php b/src/Generated/Drives/Item/Items/Item/Workbook/Tables/Add/AddRequestBuilder.php index c73efe7954e..e08b72b5239 100644 --- a/src/Generated/Drives/Item/Items/Item/Workbook/Tables/Add/AddRequestBuilder.php +++ b/src/Generated/Drives/Item/Items/Item/Workbook/Tables/Add/AddRequestBuilder.php @@ -31,12 +31,12 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Create a new table. The range source address determines the worksheet under which the table will be added. If the table can't be added (for example, because the address is invalid, or the table would overlap with another table), an error is thrown. + * Use this API to create a new Table. * @param AddPostRequestBody $body The request body * @param AddRequestBuilderPostRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception - * @link https://learn.microsoft.com/graph/api/tablecollection-add?view=graph-rest-beta Find more info here + * @link https://learn.microsoft.com/graph/api/workbook-post-tables?view=graph-rest-beta Find more info here */ public function post(AddPostRequestBody $body, ?AddRequestBuilderPostRequestConfiguration $requestConfiguration = null): Promise { $requestInfo = $this->toPostRequestInformation($body, $requestConfiguration); @@ -47,7 +47,7 @@ public function post(AddPostRequestBody $body, ?AddRequestBuilderPostRequestConf } /** - * Create a new table. The range source address determines the worksheet under which the table will be added. If the table can't be added (for example, because the address is invalid, or the table would overlap with another table), an error is thrown. + * Use this API to create a new Table. * @param AddPostRequestBody $body The request body * @param AddRequestBuilderPostRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation diff --git a/src/Generated/Drives/Item/Items/Item/Workbook/Worksheets/Item/Tables/Add/AddRequestBuilder.php b/src/Generated/Drives/Item/Items/Item/Workbook/Worksheets/Item/Tables/Add/AddRequestBuilder.php index c01e0890796..356decbd96f 100644 --- a/src/Generated/Drives/Item/Items/Item/Workbook/Worksheets/Item/Tables/Add/AddRequestBuilder.php +++ b/src/Generated/Drives/Item/Items/Item/Workbook/Worksheets/Item/Tables/Add/AddRequestBuilder.php @@ -31,12 +31,12 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Create a new table. The range source address determines the worksheet under which the table will be added. If the table can't be added (for example, because the address is invalid, or the table would overlap with another table), an error is thrown. + * Use this API to create a new Table. * @param AddPostRequestBody $body The request body * @param AddRequestBuilderPostRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception - * @link https://learn.microsoft.com/graph/api/tablecollection-add?view=graph-rest-beta Find more info here + * @link https://learn.microsoft.com/graph/api/workbook-post-tables?view=graph-rest-beta Find more info here */ public function post(AddPostRequestBody $body, ?AddRequestBuilderPostRequestConfiguration $requestConfiguration = null): Promise { $requestInfo = $this->toPostRequestInformation($body, $requestConfiguration); @@ -47,7 +47,7 @@ public function post(AddPostRequestBody $body, ?AddRequestBuilderPostRequestConf } /** - * Create a new table. The range source address determines the worksheet under which the table will be added. If the table can't be added (for example, because the address is invalid, or the table would overlap with another table), an error is thrown. + * Use this API to create a new Table. * @param AddPostRequestBody $body The request body * @param AddRequestBuilderPostRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation diff --git a/src/Generated/External/AuthorizationSystems/Item/AuthorizationSystemItemRequestBuilder.php b/src/Generated/External/AuthorizationSystems/Item/AuthorizationSystemItemRequestBuilder.php index e82d4e843f2..f5b419c8583 100644 --- a/src/Generated/External/AuthorizationSystems/Item/AuthorizationSystemItemRequestBuilder.php +++ b/src/Generated/External/AuthorizationSystems/Item/AuthorizationSystemItemRequestBuilder.php @@ -53,7 +53,7 @@ public function delete(?AuthorizationSystemItemRequestBuilderDeleteRequestConfig } /** - * Represents an onboarded AWS account, Azure subscription, or GCP project that Microsoft Entra Permissions Management will collect and analyze permissions and actions on. + * Represents an onboarded Amazon Web Services (AWS) account, Azure subscription, or Google Cloud Platform (GCP) project that Microsoft Entra Permissions Management collects and analyzes permissions and actions on. * @param AuthorizationSystemItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -100,7 +100,7 @@ public function toDeleteRequestInformation(?AuthorizationSystemItemRequestBuilde } /** - * Represents an onboarded AWS account, Azure subscription, or GCP project that Microsoft Entra Permissions Management will collect and analyze permissions and actions on. + * Represents an onboarded Amazon Web Services (AWS) account, Azure subscription, or Google Cloud Platform (GCP) project that Microsoft Entra Permissions Management collects and analyzes permissions and actions on. * @param AuthorizationSystemItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/External/AuthorizationSystems/Item/AuthorizationSystemItemRequestBuilderGetQueryParameters.php b/src/Generated/External/AuthorizationSystems/Item/AuthorizationSystemItemRequestBuilderGetQueryParameters.php index 6e2b04d805c..f0180a77b9f 100644 --- a/src/Generated/External/AuthorizationSystems/Item/AuthorizationSystemItemRequestBuilderGetQueryParameters.php +++ b/src/Generated/External/AuthorizationSystems/Item/AuthorizationSystemItemRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Represents an onboarded AWS account, Azure subscription, or GCP project that Microsoft Entra Permissions Management will collect and analyze permissions and actions on. + * Represents an onboarded Amazon Web Services (AWS) account, Azure subscription, or Google Cloud Platform (GCP) project that Microsoft Entra Permissions Management collects and analyzes permissions and actions on. */ class AuthorizationSystemItemRequestBuilderGetQueryParameters { diff --git a/src/Generated/External/Connections/Item/Schema/SchemaRequestBuilder.php b/src/Generated/External/Connections/Item/Schema/SchemaRequestBuilder.php index 26facd490f9..6d7bb079fd5 100644 --- a/src/Generated/External/Connections/Item/Schema/SchemaRequestBuilder.php +++ b/src/Generated/External/Connections/Item/Schema/SchemaRequestBuilder.php @@ -46,12 +46,12 @@ public function get(?SchemaRequestBuilderGetRequestConfiguration $requestConfigu } /** - * Create a new or update an existing schema for a Microsoft Search connection. + * Update the properties of a schema for an externalConnection. * @param Schema $body The request body * @param SchemaRequestBuilderPatchRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception - * @link https://learn.microsoft.com/graph/api/externalconnectors-externalconnection-patch-schema?view=graph-rest-beta Find more info here + * @link https://learn.microsoft.com/graph/api/externalconnectors-schema-update?view=graph-rest-beta Find more info here */ public function patch(Schema $body, ?SchemaRequestBuilderPatchRequestConfiguration $requestConfiguration = null): Promise { $requestInfo = $this->toPatchRequestInformation($body, $requestConfiguration); @@ -83,7 +83,7 @@ public function toGetRequestInformation(?SchemaRequestBuilderGetRequestConfigura } /** - * Create a new or update an existing schema for a Microsoft Search connection. + * Update the properties of a schema for an externalConnection. * @param Schema $body The request body * @param SchemaRequestBuilderPatchRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation diff --git a/src/Generated/External/IndustryData/DataConnectors/DataConnectorsRequestBuilder.php b/src/Generated/External/IndustryData/DataConnectors/DataConnectorsRequestBuilder.php index 467f2d1822f..089d28039f6 100644 --- a/src/Generated/External/IndustryData/DataConnectors/DataConnectorsRequestBuilder.php +++ b/src/Generated/External/IndustryData/DataConnectors/DataConnectorsRequestBuilder.php @@ -67,12 +67,12 @@ public function get(?DataConnectorsRequestBuilderGetRequestConfiguration $reques } /** - * Create a new azureDataLakeConnector object. + * Create a new oneRosterApiDataConnector object. * @param IndustryDataConnector $body The request body * @param DataConnectorsRequestBuilderPostRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception - * @link https://learn.microsoft.com/graph/api/industrydata-azuredatalakeconnector-post?view=graph-rest-beta Find more info here + * @link https://learn.microsoft.com/graph/api/industrydata-onerosterapidataconnector-post?view=graph-rest-beta Find more info here */ public function post(IndustryDataConnector $body, ?DataConnectorsRequestBuilderPostRequestConfiguration $requestConfiguration = null): Promise { $requestInfo = $this->toPostRequestInformation($body, $requestConfiguration); @@ -104,7 +104,7 @@ public function toGetRequestInformation(?DataConnectorsRequestBuilderGetRequestC } /** - * Create a new azureDataLakeConnector object. + * Create a new oneRosterApiDataConnector object. * @param IndustryDataConnector $body The request body * @param DataConnectorsRequestBuilderPostRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation diff --git a/src/Generated/External/IndustryData/InboundFlows/InboundFlowsRequestBuilder.php b/src/Generated/External/IndustryData/InboundFlows/InboundFlowsRequestBuilder.php index de7d21bcaed..0ad8a25982d 100644 --- a/src/Generated/External/IndustryData/InboundFlows/InboundFlowsRequestBuilder.php +++ b/src/Generated/External/IndustryData/InboundFlows/InboundFlowsRequestBuilder.php @@ -67,12 +67,12 @@ public function get(?InboundFlowsRequestBuilderGetRequestConfiguration $requestC } /** - * Create a new inboundFileFlow object. + * Create a new inboundApiFlow object. * @param InboundFlow $body The request body * @param InboundFlowsRequestBuilderPostRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception - * @link https://learn.microsoft.com/graph/api/industrydata-inboundfileflow-post?view=graph-rest-beta Find more info here + * @link https://learn.microsoft.com/graph/api/industrydata-inboundapiflow-post?view=graph-rest-beta Find more info here */ public function post(InboundFlow $body, ?InboundFlowsRequestBuilderPostRequestConfiguration $requestConfiguration = null): Promise { $requestInfo = $this->toPostRequestInformation($body, $requestConfiguration); @@ -104,7 +104,7 @@ public function toGetRequestInformation(?InboundFlowsRequestBuilderGetRequestCon } /** - * Create a new inboundFileFlow object. + * Create a new inboundApiFlow object. * @param InboundFlow $body The request body * @param InboundFlowsRequestBuilderPostRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation diff --git a/src/Generated/Groups/GroupsRequestBuilder.php b/src/Generated/Groups/GroupsRequestBuilder.php index e484e11c847..d7217fcbcb1 100644 --- a/src/Generated/Groups/GroupsRequestBuilder.php +++ b/src/Generated/Groups/GroupsRequestBuilder.php @@ -107,12 +107,12 @@ public function get(?GroupsRequestBuilderGetRequestConfiguration $requestConfigu } /** - * Create a new group object if it doesn't exist, or update the properties of an existing group object.You can create or update the following types of group: By default, this operation returns only a subset of the properties for each group. For a list of properties that are returned by default, see the Properties section of the group resource. To get properties that are not returned by default, do a GET operation and specify the properties in a $select OData query option. + * Create a new group as specified in the request body. You can create one of the following groups: This operation returns by default only a subset of the properties for each group. These default properties are noted in the Properties section. To get properties that are not returned by default, do a GET operation and specify the properties in a $select OData query option. Note: To create a team, first create a group then add a team to it, see create team. * @param Group $body The request body * @param GroupsRequestBuilderPostRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception - * @link https://learn.microsoft.com/graph/api/group-upsert?view=graph-rest-beta Find more info here + * @link https://learn.microsoft.com/graph/api/group-post-groups?view=graph-rest-beta Find more info here */ public function post(Group $body, ?GroupsRequestBuilderPostRequestConfiguration $requestConfiguration = null): Promise { $requestInfo = $this->toPostRequestInformation($body, $requestConfiguration); @@ -144,7 +144,7 @@ public function toGetRequestInformation(?GroupsRequestBuilderGetRequestConfigura } /** - * Create a new group object if it doesn't exist, or update the properties of an existing group object.You can create or update the following types of group: By default, this operation returns only a subset of the properties for each group. For a list of properties that are returned by default, see the Properties section of the group resource. To get properties that are not returned by default, do a GET operation and specify the properties in a $select OData query option. + * Create a new group as specified in the request body. You can create one of the following groups: This operation returns by default only a subset of the properties for each group. These default properties are noted in the Properties section. To get properties that are not returned by default, do a GET operation and specify the properties in a $select OData query option. Note: To create a team, first create a group then add a team to it, see create team. * @param Group $body The request body * @param GroupsRequestBuilderPostRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation diff --git a/src/Generated/Groups/Item/Calendar/CalendarView/Delta/DeltaRequestBuilder.php b/src/Generated/Groups/Item/Calendar/CalendarView/Delta/DeltaRequestBuilder.php index a38a2d62656..f7f64e7df8e 100644 --- a/src/Generated/Groups/Item/Calendar/CalendarView/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Groups/Item/Calendar/CalendarView/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Groups/Item/Calendar/CalendarView/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Groups/Item/Calendar/CalendarView/Delta/DeltaRequestBuilderGetQueryParameters.php index 0ee03446ee7..46aa083f67b 100644 --- a/src/Generated/Groups/Item/Calendar/CalendarView/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Groups/Item/Calendar/CalendarView/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Groups/Item/Calendar/CalendarView/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php b/src/Generated/Groups/Item/Calendar/CalendarView/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php index 8d5312e69af..ae19bad29e3 100644 --- a/src/Generated/Groups/Item/Calendar/CalendarView/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Groups/Item/Calendar/CalendarView/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Groups/Item/Calendar/CalendarView/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Groups/Item/Calendar/CalendarView/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php index ba6acebae15..7d2f0b715b1 100644 --- a/src/Generated/Groups/Item/Calendar/CalendarView/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Groups/Item/Calendar/CalendarView/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Groups/Item/Calendar/CalendarView/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilder.php b/src/Generated/Groups/Item/Calendar/CalendarView/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilder.php index 99254e1f7cc..1c46654eadd 100644 --- a/src/Generated/Groups/Item/Calendar/CalendarView/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Groups/Item/Calendar/CalendarView/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Groups/Item/Calendar/CalendarView/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Groups/Item/Calendar/CalendarView/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php index 597430bd718..68c1e4e350b 100644 --- a/src/Generated/Groups/Item/Calendar/CalendarView/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Groups/Item/Calendar/CalendarView/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Groups/Item/Calendar/CalendarView/Item/Instances/Delta/DeltaRequestBuilder.php b/src/Generated/Groups/Item/Calendar/CalendarView/Item/Instances/Delta/DeltaRequestBuilder.php index 0bf5fe3e230..f3ea4235608 100644 --- a/src/Generated/Groups/Item/Calendar/CalendarView/Item/Instances/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Groups/Item/Calendar/CalendarView/Item/Instances/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Groups/Item/Calendar/CalendarView/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Groups/Item/Calendar/CalendarView/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php index 041af381857..66ee470a827 100644 --- a/src/Generated/Groups/Item/Calendar/CalendarView/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Groups/Item/Calendar/CalendarView/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Groups/Item/Calendar/CalendarView/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php b/src/Generated/Groups/Item/Calendar/CalendarView/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php index c255d483b4a..5faa314453a 100644 --- a/src/Generated/Groups/Item/Calendar/CalendarView/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Groups/Item/Calendar/CalendarView/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Groups/Item/Calendar/CalendarView/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Groups/Item/Calendar/CalendarView/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php index 11a025b0a32..e5c8ef55f91 100644 --- a/src/Generated/Groups/Item/Calendar/CalendarView/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Groups/Item/Calendar/CalendarView/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Groups/Item/Calendar/Events/Delta/DeltaRequestBuilder.php b/src/Generated/Groups/Item/Calendar/Events/Delta/DeltaRequestBuilder.php index b579389b7f5..48d57218bd6 100644 --- a/src/Generated/Groups/Item/Calendar/Events/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Groups/Item/Calendar/Events/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Groups/Item/Calendar/Events/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Groups/Item/Calendar/Events/Delta/DeltaRequestBuilderGetQueryParameters.php index 8281efa1459..66a5ec2e276 100644 --- a/src/Generated/Groups/Item/Calendar/Events/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Groups/Item/Calendar/Events/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Groups/Item/Calendar/Events/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php b/src/Generated/Groups/Item/Calendar/Events/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php index 973644ed809..950fe46e5b8 100644 --- a/src/Generated/Groups/Item/Calendar/Events/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Groups/Item/Calendar/Events/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Groups/Item/Calendar/Events/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Groups/Item/Calendar/Events/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php index c48a2fd54af..1a944659bf6 100644 --- a/src/Generated/Groups/Item/Calendar/Events/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Groups/Item/Calendar/Events/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Groups/Item/Calendar/Events/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilder.php b/src/Generated/Groups/Item/Calendar/Events/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilder.php index dfbd7271250..458096a39d0 100644 --- a/src/Generated/Groups/Item/Calendar/Events/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Groups/Item/Calendar/Events/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Groups/Item/Calendar/Events/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Groups/Item/Calendar/Events/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php index 1f78fae866e..188e16d350a 100644 --- a/src/Generated/Groups/Item/Calendar/Events/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Groups/Item/Calendar/Events/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Groups/Item/Calendar/Events/Item/Instances/Delta/DeltaRequestBuilder.php b/src/Generated/Groups/Item/Calendar/Events/Item/Instances/Delta/DeltaRequestBuilder.php index a93618bda96..add4038fb11 100644 --- a/src/Generated/Groups/Item/Calendar/Events/Item/Instances/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Groups/Item/Calendar/Events/Item/Instances/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Groups/Item/Calendar/Events/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Groups/Item/Calendar/Events/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php index c793ec16255..2ba0986b5bd 100644 --- a/src/Generated/Groups/Item/Calendar/Events/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Groups/Item/Calendar/Events/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Groups/Item/Calendar/Events/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php b/src/Generated/Groups/Item/Calendar/Events/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php index db7c3ca273c..46eb884cb7a 100644 --- a/src/Generated/Groups/Item/Calendar/Events/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Groups/Item/Calendar/Events/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Groups/Item/Calendar/Events/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Groups/Item/Calendar/Events/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php index 439b455196a..38995010400 100644 --- a/src/Generated/Groups/Item/Calendar/Events/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Groups/Item/Calendar/Events/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Groups/Item/CalendarView/Delta/DeltaRequestBuilder.php b/src/Generated/Groups/Item/CalendarView/Delta/DeltaRequestBuilder.php index 2c0a398beb1..abf8814d1d8 100644 --- a/src/Generated/Groups/Item/CalendarView/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Groups/Item/CalendarView/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Groups/Item/CalendarView/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Groups/Item/CalendarView/Delta/DeltaRequestBuilderGetQueryParameters.php index f3677e4aed8..2b0ad0763c8 100644 --- a/src/Generated/Groups/Item/CalendarView/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Groups/Item/CalendarView/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Groups/Item/CalendarView/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php b/src/Generated/Groups/Item/CalendarView/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php index f966e46462b..700d426330b 100644 --- a/src/Generated/Groups/Item/CalendarView/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Groups/Item/CalendarView/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Groups/Item/CalendarView/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Groups/Item/CalendarView/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php index 8cb123454f2..2fce0728e17 100644 --- a/src/Generated/Groups/Item/CalendarView/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Groups/Item/CalendarView/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Groups/Item/CalendarView/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilder.php b/src/Generated/Groups/Item/CalendarView/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilder.php index b88c5075e0b..7d8a380218b 100644 --- a/src/Generated/Groups/Item/CalendarView/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Groups/Item/CalendarView/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Groups/Item/CalendarView/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Groups/Item/CalendarView/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php index 16a050165ce..aad130f5cf0 100644 --- a/src/Generated/Groups/Item/CalendarView/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Groups/Item/CalendarView/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Groups/Item/CalendarView/Item/Instances/Delta/DeltaRequestBuilder.php b/src/Generated/Groups/Item/CalendarView/Item/Instances/Delta/DeltaRequestBuilder.php index fbf2cc2bcd2..a6845d981ef 100644 --- a/src/Generated/Groups/Item/CalendarView/Item/Instances/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Groups/Item/CalendarView/Item/Instances/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Groups/Item/CalendarView/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Groups/Item/CalendarView/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php index 83f2eb9eaa6..b8f5e8ed22d 100644 --- a/src/Generated/Groups/Item/CalendarView/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Groups/Item/CalendarView/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Groups/Item/CalendarView/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php b/src/Generated/Groups/Item/CalendarView/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php index 2fb8c87fb0c..5cffe29db8c 100644 --- a/src/Generated/Groups/Item/CalendarView/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Groups/Item/CalendarView/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Groups/Item/CalendarView/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Groups/Item/CalendarView/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php index 5a9a1497d9a..0547d1cd15f 100644 --- a/src/Generated/Groups/Item/CalendarView/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Groups/Item/CalendarView/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Groups/Item/Conversations/ConversationsRequestBuilder.php b/src/Generated/Groups/Item/Conversations/ConversationsRequestBuilder.php index 232151dfb25..3d4b6e9938c 100644 --- a/src/Generated/Groups/Item/Conversations/ConversationsRequestBuilder.php +++ b/src/Generated/Groups/Item/Conversations/ConversationsRequestBuilder.php @@ -67,12 +67,12 @@ public function get(?ConversationsRequestBuilderGetRequestConfiguration $request } /** - * Create a new conversation by including a thread and a post. Use reply thread or reply post to further post to that conversation. + * Create an open extension (openTypeExtension object) and add custom properties in a new or existing instance of a resource. You can create an open extension in a resource instance and store custom data to it all in the same operation, except for specific resources. The table in the Permissions section lists the resources that support open extensions. * @param Conversation $body The request body * @param ConversationsRequestBuilderPostRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception - * @link https://learn.microsoft.com/graph/api/group-post-conversations?view=graph-rest-beta Find more info here + * @link https://learn.microsoft.com/graph/api/opentypeextension-post-opentypeextension?view=graph-rest-beta Find more info here */ public function post(Conversation $body, ?ConversationsRequestBuilderPostRequestConfiguration $requestConfiguration = null): Promise { $requestInfo = $this->toPostRequestInformation($body, $requestConfiguration); @@ -104,7 +104,7 @@ public function toGetRequestInformation(?ConversationsRequestBuilderGetRequestCo } /** - * Create a new conversation by including a thread and a post. Use reply thread or reply post to further post to that conversation. + * Create an open extension (openTypeExtension object) and add custom properties in a new or existing instance of a resource. You can create an open extension in a resource instance and store custom data to it all in the same operation, except for specific resources. The table in the Permissions section lists the resources that support open extensions. * @param Conversation $body The request body * @param ConversationsRequestBuilderPostRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation diff --git a/src/Generated/Groups/Item/Conversations/Item/ConversationItemRequestBuilder.php b/src/Generated/Groups/Item/Conversations/Item/ConversationItemRequestBuilder.php index cc190f8ef54..ccc2cb5c328 100644 --- a/src/Generated/Groups/Item/Conversations/Item/ConversationItemRequestBuilder.php +++ b/src/Generated/Groups/Item/Conversations/Item/ConversationItemRequestBuilder.php @@ -39,11 +39,11 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Delete conversation. + * Delete a group's conversation object. * @param ConversationItemRequestBuilderDeleteRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception - * @link https://learn.microsoft.com/graph/api/conversation-delete?view=graph-rest-beta Find more info here + * @link https://learn.microsoft.com/graph/api/group-delete-conversation?view=graph-rest-beta Find more info here */ public function delete(?ConversationItemRequestBuilderDeleteRequestConfiguration $requestConfiguration = null): Promise { $requestInfo = $this->toDeleteRequestInformation($requestConfiguration); @@ -54,11 +54,11 @@ public function delete(?ConversationItemRequestBuilderDeleteRequestConfiguration } /** - * Retrieve the properties and relationships of conversation object. + * Get a group's conversation object. * @param ConversationItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception - * @link https://learn.microsoft.com/graph/api/conversation-get?view=graph-rest-beta Find more info here + * @link https://learn.microsoft.com/graph/api/group-get-conversation?view=graph-rest-beta Find more info here */ public function get(?ConversationItemRequestBuilderGetRequestConfiguration $requestConfiguration = null): Promise { $requestInfo = $this->toGetRequestInformation($requestConfiguration); @@ -69,7 +69,7 @@ public function get(?ConversationItemRequestBuilderGetRequestConfiguration $requ } /** - * Delete conversation. + * Delete a group's conversation object. * @param ConversationItemRequestBuilderDeleteRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ @@ -87,7 +87,7 @@ public function toDeleteRequestInformation(?ConversationItemRequestBuilderDelete } /** - * Retrieve the properties and relationships of conversation object. + * Get a group's conversation object. * @param ConversationItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Groups/Item/Conversations/Item/ConversationItemRequestBuilderGetQueryParameters.php b/src/Generated/Groups/Item/Conversations/Item/ConversationItemRequestBuilderGetQueryParameters.php index e28c0cfb775..b72016b3ba5 100644 --- a/src/Generated/Groups/Item/Conversations/Item/ConversationItemRequestBuilderGetQueryParameters.php +++ b/src/Generated/Groups/Item/Conversations/Item/ConversationItemRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Retrieve the properties and relationships of conversation object. + * Get a group's conversation object. */ class ConversationItemRequestBuilderGetQueryParameters { diff --git a/src/Generated/Groups/Item/Conversations/Item/Threads/Item/Reply/ReplyRequestBuilder.php b/src/Generated/Groups/Item/Conversations/Item/Threads/Item/Reply/ReplyRequestBuilder.php index df1b4b7acf4..4bafb856eea 100644 --- a/src/Generated/Groups/Item/Conversations/Item/Threads/Item/Reply/ReplyRequestBuilder.php +++ b/src/Generated/Groups/Item/Conversations/Item/Threads/Item/Reply/ReplyRequestBuilder.php @@ -30,12 +30,12 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Create an open extension (openTypeExtension object) and add custom properties in a new or existing instance of a resource. You can create an open extension in a resource instance and store custom data to it all in the same operation, except for specific resources. The table in the Permissions section lists the resources that support open extensions. + * Reply to a post and add a new post to the specified thread in a group conversation. You can specify both the parent conversation and thread in the request, or, you can specify just the parent thread without the parent conversation. * @param ReplyPostRequestBody $body The request body * @param ReplyRequestBuilderPostRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception - * @link https://learn.microsoft.com/graph/api/opentypeextension-post-opentypeextension?view=graph-rest-beta Find more info here + * @link https://learn.microsoft.com/graph/api/post-reply?view=graph-rest-beta Find more info here */ public function post(ReplyPostRequestBody $body, ?ReplyRequestBuilderPostRequestConfiguration $requestConfiguration = null): Promise { $requestInfo = $this->toPostRequestInformation($body, $requestConfiguration); @@ -46,7 +46,7 @@ public function post(ReplyPostRequestBody $body, ?ReplyRequestBuilderPostRequest } /** - * Create an open extension (openTypeExtension object) and add custom properties in a new or existing instance of a resource. You can create an open extension in a resource instance and store custom data to it all in the same operation, except for specific resources. The table in the Permissions section lists the resources that support open extensions. + * Reply to a post and add a new post to the specified thread in a group conversation. You can specify both the parent conversation and thread in the request, or, you can specify just the parent thread without the parent conversation. * @param ReplyPostRequestBody $body The request body * @param ReplyRequestBuilderPostRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation diff --git a/src/Generated/Groups/Item/Events/Delta/DeltaRequestBuilder.php b/src/Generated/Groups/Item/Events/Delta/DeltaRequestBuilder.php index aeefb4b515f..cab1264f0d7 100644 --- a/src/Generated/Groups/Item/Events/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Groups/Item/Events/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Groups/Item/Events/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Groups/Item/Events/Delta/DeltaRequestBuilderGetQueryParameters.php index d09fd839b01..a0a43ef238e 100644 --- a/src/Generated/Groups/Item/Events/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Groups/Item/Events/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Groups/Item/Events/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php b/src/Generated/Groups/Item/Events/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php index 5a3e342575b..b1870590400 100644 --- a/src/Generated/Groups/Item/Events/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Groups/Item/Events/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Groups/Item/Events/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Groups/Item/Events/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php index 343bfbfe44e..150c1c820dd 100644 --- a/src/Generated/Groups/Item/Events/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Groups/Item/Events/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Groups/Item/Events/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilder.php b/src/Generated/Groups/Item/Events/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilder.php index c75bc869f0c..258908fe9d1 100644 --- a/src/Generated/Groups/Item/Events/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Groups/Item/Events/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Groups/Item/Events/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Groups/Item/Events/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php index 9439f73732a..c1b962909e7 100644 --- a/src/Generated/Groups/Item/Events/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Groups/Item/Events/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Groups/Item/Events/Item/Instances/Delta/DeltaRequestBuilder.php b/src/Generated/Groups/Item/Events/Item/Instances/Delta/DeltaRequestBuilder.php index dd249e7b873..8c0e8aff31f 100644 --- a/src/Generated/Groups/Item/Events/Item/Instances/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Groups/Item/Events/Item/Instances/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Groups/Item/Events/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Groups/Item/Events/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php index dd3c36a5be2..ce661fc4e9b 100644 --- a/src/Generated/Groups/Item/Events/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Groups/Item/Events/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Groups/Item/Events/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php b/src/Generated/Groups/Item/Events/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php index a97affd5f5d..e402185b319 100644 --- a/src/Generated/Groups/Item/Events/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Groups/Item/Events/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Groups/Item/Events/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Groups/Item/Events/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php index c4f91276145..d41c1c76a64 100644 --- a/src/Generated/Groups/Item/Events/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Groups/Item/Events/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Groups/Item/Onenote/Notebooks/Item/NotebookItemRequestBuilder.php b/src/Generated/Groups/Item/Onenote/Notebooks/Item/NotebookItemRequestBuilder.php index c4d0b9d865d..9c7868a788b 100644 --- a/src/Generated/Groups/Item/Onenote/Notebooks/Item/NotebookItemRequestBuilder.php +++ b/src/Generated/Groups/Item/Onenote/Notebooks/Item/NotebookItemRequestBuilder.php @@ -69,7 +69,7 @@ public function delete(?NotebookItemRequestBuilderDeleteRequestConfiguration $re } /** - * The collection of OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The collection of OneNote notebooks that the user or group owns. Read-only. Nullable. * @param NotebookItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -116,7 +116,7 @@ public function toDeleteRequestInformation(?NotebookItemRequestBuilderDeleteRequ } /** - * The collection of OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The collection of OneNote notebooks that the user or group owns. Read-only. Nullable. * @param NotebookItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Groups/Item/Onenote/Notebooks/Item/NotebookItemRequestBuilderGetQueryParameters.php b/src/Generated/Groups/Item/Onenote/Notebooks/Item/NotebookItemRequestBuilderGetQueryParameters.php index 8aa23f2b2c4..f543cf9de14 100644 --- a/src/Generated/Groups/Item/Onenote/Notebooks/Item/NotebookItemRequestBuilderGetQueryParameters.php +++ b/src/Generated/Groups/Item/Onenote/Notebooks/Item/NotebookItemRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * The collection of OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The collection of OneNote notebooks that the user or group owns. Read-only. Nullable. */ class NotebookItemRequestBuilderGetQueryParameters { diff --git a/src/Generated/Groups/Item/Onenote/Notebooks/NotebooksRequestBuilder.php b/src/Generated/Groups/Item/Onenote/Notebooks/NotebooksRequestBuilder.php index b2473370617..3401c62d47d 100644 --- a/src/Generated/Groups/Item/Onenote/Notebooks/NotebooksRequestBuilder.php +++ b/src/Generated/Groups/Item/Onenote/Notebooks/NotebooksRequestBuilder.php @@ -61,7 +61,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * The collection of OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The collection of OneNote notebooks that the user or group owns. Read-only. Nullable. * @param NotebooksRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -99,7 +99,7 @@ public function post(Notebook $body, ?NotebooksRequestBuilderPostRequestConfigur } /** - * The collection of OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The collection of OneNote notebooks that the user or group owns. Read-only. Nullable. * @param NotebooksRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Groups/Item/Onenote/Notebooks/NotebooksRequestBuilderGetQueryParameters.php b/src/Generated/Groups/Item/Onenote/Notebooks/NotebooksRequestBuilderGetQueryParameters.php index 59cc2654668..f129f242754 100644 --- a/src/Generated/Groups/Item/Onenote/Notebooks/NotebooksRequestBuilderGetQueryParameters.php +++ b/src/Generated/Groups/Item/Onenote/Notebooks/NotebooksRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * The collection of OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The collection of OneNote notebooks that the user or group owns. Read-only. Nullable. */ class NotebooksRequestBuilderGetQueryParameters { diff --git a/src/Generated/Groups/Item/Onenote/Pages/Item/OnenotePageItemRequestBuilder.php b/src/Generated/Groups/Item/Onenote/Pages/Item/OnenotePageItemRequestBuilder.php index 43c14d22b37..4b5fe4e72f8 100644 --- a/src/Generated/Groups/Item/Onenote/Pages/Item/OnenotePageItemRequestBuilder.php +++ b/src/Generated/Groups/Item/Onenote/Pages/Item/OnenotePageItemRequestBuilder.php @@ -93,7 +93,7 @@ public function delete(?OnenotePageItemRequestBuilderDeleteRequestConfiguration } /** - * The pages in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The pages in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @param OnenotePageItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -140,7 +140,7 @@ public function toDeleteRequestInformation(?OnenotePageItemRequestBuilderDeleteR } /** - * The pages in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The pages in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @param OnenotePageItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Groups/Item/Onenote/Pages/Item/OnenotePageItemRequestBuilderGetQueryParameters.php b/src/Generated/Groups/Item/Onenote/Pages/Item/OnenotePageItemRequestBuilderGetQueryParameters.php index 7d84a86e89a..7c6bb1be082 100644 --- a/src/Generated/Groups/Item/Onenote/Pages/Item/OnenotePageItemRequestBuilderGetQueryParameters.php +++ b/src/Generated/Groups/Item/Onenote/Pages/Item/OnenotePageItemRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * The pages in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The pages in all OneNote notebooks that the user or group owns. Read-only. Nullable. */ class OnenotePageItemRequestBuilderGetQueryParameters { diff --git a/src/Generated/Groups/Item/Onenote/Pages/PagesRequestBuilder.php b/src/Generated/Groups/Item/Onenote/Pages/PagesRequestBuilder.php index 081e9cdf9e3..d6baf9eee5d 100644 --- a/src/Generated/Groups/Item/Onenote/Pages/PagesRequestBuilder.php +++ b/src/Generated/Groups/Item/Onenote/Pages/PagesRequestBuilder.php @@ -52,7 +52,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * The pages in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The pages in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @param PagesRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -81,7 +81,7 @@ public function post(OnenotePage $body, ?PagesRequestBuilderPostRequestConfigura } /** - * The pages in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The pages in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @param PagesRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Groups/Item/Onenote/Pages/PagesRequestBuilderGetQueryParameters.php b/src/Generated/Groups/Item/Onenote/Pages/PagesRequestBuilderGetQueryParameters.php index 652ee6b7806..500cf67f976 100644 --- a/src/Generated/Groups/Item/Onenote/Pages/PagesRequestBuilderGetQueryParameters.php +++ b/src/Generated/Groups/Item/Onenote/Pages/PagesRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * The pages in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The pages in all OneNote notebooks that the user or group owns. Read-only. Nullable. */ class PagesRequestBuilderGetQueryParameters { diff --git a/src/Generated/Groups/Item/Onenote/SectionGroups/Item/SectionGroupItemRequestBuilder.php b/src/Generated/Groups/Item/Onenote/SectionGroups/Item/SectionGroupItemRequestBuilder.php index 05d9d19047c..40bf6c700f8 100644 --- a/src/Generated/Groups/Item/Onenote/SectionGroups/Item/SectionGroupItemRequestBuilder.php +++ b/src/Generated/Groups/Item/Onenote/SectionGroups/Item/SectionGroupItemRequestBuilder.php @@ -77,7 +77,7 @@ public function delete(?SectionGroupItemRequestBuilderDeleteRequestConfiguration } /** - * The section groups in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The section groups in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @param SectionGroupItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -124,7 +124,7 @@ public function toDeleteRequestInformation(?SectionGroupItemRequestBuilderDelete } /** - * The section groups in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The section groups in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @param SectionGroupItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Groups/Item/Onenote/SectionGroups/Item/SectionGroupItemRequestBuilderGetQueryParameters.php b/src/Generated/Groups/Item/Onenote/SectionGroups/Item/SectionGroupItemRequestBuilderGetQueryParameters.php index 73f4d1c9f90..6487a8de945 100644 --- a/src/Generated/Groups/Item/Onenote/SectionGroups/Item/SectionGroupItemRequestBuilderGetQueryParameters.php +++ b/src/Generated/Groups/Item/Onenote/SectionGroups/Item/SectionGroupItemRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * The section groups in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The section groups in all OneNote notebooks that the user or group owns. Read-only. Nullable. */ class SectionGroupItemRequestBuilderGetQueryParameters { diff --git a/src/Generated/Groups/Item/Onenote/SectionGroups/SectionGroupsRequestBuilder.php b/src/Generated/Groups/Item/Onenote/SectionGroups/SectionGroupsRequestBuilder.php index 5b23d2df108..1b62748b40a 100644 --- a/src/Generated/Groups/Item/Onenote/SectionGroups/SectionGroupsRequestBuilder.php +++ b/src/Generated/Groups/Item/Onenote/SectionGroups/SectionGroupsRequestBuilder.php @@ -52,7 +52,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * The section groups in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The section groups in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @param SectionGroupsRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -81,7 +81,7 @@ public function post(SectionGroup $body, ?SectionGroupsRequestBuilderPostRequest } /** - * The section groups in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The section groups in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @param SectionGroupsRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Groups/Item/Onenote/SectionGroups/SectionGroupsRequestBuilderGetQueryParameters.php b/src/Generated/Groups/Item/Onenote/SectionGroups/SectionGroupsRequestBuilderGetQueryParameters.php index 110281e6ec5..991fbe1bd45 100644 --- a/src/Generated/Groups/Item/Onenote/SectionGroups/SectionGroupsRequestBuilderGetQueryParameters.php +++ b/src/Generated/Groups/Item/Onenote/SectionGroups/SectionGroupsRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * The section groups in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The section groups in all OneNote notebooks that the user or group owns. Read-only. Nullable. */ class SectionGroupsRequestBuilderGetQueryParameters { diff --git a/src/Generated/Groups/Item/Onenote/Sections/Item/OnenoteSectionItemRequestBuilder.php b/src/Generated/Groups/Item/Onenote/Sections/Item/OnenoteSectionItemRequestBuilder.php index 32e2df813a3..78ad9718a9d 100644 --- a/src/Generated/Groups/Item/Onenote/Sections/Item/OnenoteSectionItemRequestBuilder.php +++ b/src/Generated/Groups/Item/Onenote/Sections/Item/OnenoteSectionItemRequestBuilder.php @@ -85,7 +85,7 @@ public function delete(?OnenoteSectionItemRequestBuilderDeleteRequestConfigurati } /** - * The sections in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The sections in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @param OnenoteSectionItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -132,7 +132,7 @@ public function toDeleteRequestInformation(?OnenoteSectionItemRequestBuilderDele } /** - * The sections in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The sections in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @param OnenoteSectionItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Groups/Item/Onenote/Sections/Item/OnenoteSectionItemRequestBuilderGetQueryParameters.php b/src/Generated/Groups/Item/Onenote/Sections/Item/OnenoteSectionItemRequestBuilderGetQueryParameters.php index 059e6236c31..bfc5a708441 100644 --- a/src/Generated/Groups/Item/Onenote/Sections/Item/OnenoteSectionItemRequestBuilderGetQueryParameters.php +++ b/src/Generated/Groups/Item/Onenote/Sections/Item/OnenoteSectionItemRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * The sections in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The sections in all OneNote notebooks that the user or group owns. Read-only. Nullable. */ class OnenoteSectionItemRequestBuilderGetQueryParameters { diff --git a/src/Generated/Groups/Item/Onenote/Sections/SectionsRequestBuilder.php b/src/Generated/Groups/Item/Onenote/Sections/SectionsRequestBuilder.php index bb43d874e01..e5c77d1d7e4 100644 --- a/src/Generated/Groups/Item/Onenote/Sections/SectionsRequestBuilder.php +++ b/src/Generated/Groups/Item/Onenote/Sections/SectionsRequestBuilder.php @@ -52,7 +52,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * The sections in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The sections in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @param SectionsRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -81,7 +81,7 @@ public function post(OnenoteSection $body, ?SectionsRequestBuilderPostRequestCon } /** - * The sections in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The sections in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @param SectionsRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Groups/Item/Onenote/Sections/SectionsRequestBuilderGetQueryParameters.php b/src/Generated/Groups/Item/Onenote/Sections/SectionsRequestBuilderGetQueryParameters.php index 17d3cb02e45..79eba56e362 100644 --- a/src/Generated/Groups/Item/Onenote/Sections/SectionsRequestBuilderGetQueryParameters.php +++ b/src/Generated/Groups/Item/Onenote/Sections/SectionsRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * The sections in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The sections in all OneNote notebooks that the user or group owns. Read-only. Nullable. */ class SectionsRequestBuilderGetQueryParameters { diff --git a/src/Generated/Groups/Item/Sites/Item/Onenote/Notebooks/Item/NotebookItemRequestBuilder.php b/src/Generated/Groups/Item/Sites/Item/Onenote/Notebooks/Item/NotebookItemRequestBuilder.php index 84b2880c4c8..ac4dc48ffbf 100644 --- a/src/Generated/Groups/Item/Sites/Item/Onenote/Notebooks/Item/NotebookItemRequestBuilder.php +++ b/src/Generated/Groups/Item/Sites/Item/Onenote/Notebooks/Item/NotebookItemRequestBuilder.php @@ -69,7 +69,7 @@ public function delete(?NotebookItemRequestBuilderDeleteRequestConfiguration $re } /** - * The collection of OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The collection of OneNote notebooks that the user or group owns. Read-only. Nullable. * @param NotebookItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -116,7 +116,7 @@ public function toDeleteRequestInformation(?NotebookItemRequestBuilderDeleteRequ } /** - * The collection of OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The collection of OneNote notebooks that the user or group owns. Read-only. Nullable. * @param NotebookItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Groups/Item/Sites/Item/Onenote/Notebooks/Item/NotebookItemRequestBuilderGetQueryParameters.php b/src/Generated/Groups/Item/Sites/Item/Onenote/Notebooks/Item/NotebookItemRequestBuilderGetQueryParameters.php index d385d17081d..e5c54d0eafe 100644 --- a/src/Generated/Groups/Item/Sites/Item/Onenote/Notebooks/Item/NotebookItemRequestBuilderGetQueryParameters.php +++ b/src/Generated/Groups/Item/Sites/Item/Onenote/Notebooks/Item/NotebookItemRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * The collection of OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The collection of OneNote notebooks that the user or group owns. Read-only. Nullable. */ class NotebookItemRequestBuilderGetQueryParameters { diff --git a/src/Generated/Groups/Item/Sites/Item/Onenote/Notebooks/NotebooksRequestBuilder.php b/src/Generated/Groups/Item/Sites/Item/Onenote/Notebooks/NotebooksRequestBuilder.php index 9625744828b..3941b02e205 100644 --- a/src/Generated/Groups/Item/Sites/Item/Onenote/Notebooks/NotebooksRequestBuilder.php +++ b/src/Generated/Groups/Item/Sites/Item/Onenote/Notebooks/NotebooksRequestBuilder.php @@ -61,7 +61,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * The collection of OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The collection of OneNote notebooks that the user or group owns. Read-only. Nullable. * @param NotebooksRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -99,7 +99,7 @@ public function post(Notebook $body, ?NotebooksRequestBuilderPostRequestConfigur } /** - * The collection of OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The collection of OneNote notebooks that the user or group owns. Read-only. Nullable. * @param NotebooksRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Groups/Item/Sites/Item/Onenote/Notebooks/NotebooksRequestBuilderGetQueryParameters.php b/src/Generated/Groups/Item/Sites/Item/Onenote/Notebooks/NotebooksRequestBuilderGetQueryParameters.php index 18a4d234dff..43c51f163fb 100644 --- a/src/Generated/Groups/Item/Sites/Item/Onenote/Notebooks/NotebooksRequestBuilderGetQueryParameters.php +++ b/src/Generated/Groups/Item/Sites/Item/Onenote/Notebooks/NotebooksRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * The collection of OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The collection of OneNote notebooks that the user or group owns. Read-only. Nullable. */ class NotebooksRequestBuilderGetQueryParameters { diff --git a/src/Generated/Groups/Item/Sites/Item/Onenote/Pages/Item/OnenotePageItemRequestBuilder.php b/src/Generated/Groups/Item/Sites/Item/Onenote/Pages/Item/OnenotePageItemRequestBuilder.php index e34162e24f4..65bfefdc896 100644 --- a/src/Generated/Groups/Item/Sites/Item/Onenote/Pages/Item/OnenotePageItemRequestBuilder.php +++ b/src/Generated/Groups/Item/Sites/Item/Onenote/Pages/Item/OnenotePageItemRequestBuilder.php @@ -93,7 +93,7 @@ public function delete(?OnenotePageItemRequestBuilderDeleteRequestConfiguration } /** - * The pages in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The pages in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @param OnenotePageItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -140,7 +140,7 @@ public function toDeleteRequestInformation(?OnenotePageItemRequestBuilderDeleteR } /** - * The pages in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The pages in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @param OnenotePageItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Groups/Item/Sites/Item/Onenote/Pages/Item/OnenotePageItemRequestBuilderGetQueryParameters.php b/src/Generated/Groups/Item/Sites/Item/Onenote/Pages/Item/OnenotePageItemRequestBuilderGetQueryParameters.php index 83a620039fd..542a5a9bac2 100644 --- a/src/Generated/Groups/Item/Sites/Item/Onenote/Pages/Item/OnenotePageItemRequestBuilderGetQueryParameters.php +++ b/src/Generated/Groups/Item/Sites/Item/Onenote/Pages/Item/OnenotePageItemRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * The pages in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The pages in all OneNote notebooks that the user or group owns. Read-only. Nullable. */ class OnenotePageItemRequestBuilderGetQueryParameters { diff --git a/src/Generated/Groups/Item/Sites/Item/Onenote/Pages/PagesRequestBuilder.php b/src/Generated/Groups/Item/Sites/Item/Onenote/Pages/PagesRequestBuilder.php index 2ba2637a9b3..0f6c492e3d4 100644 --- a/src/Generated/Groups/Item/Sites/Item/Onenote/Pages/PagesRequestBuilder.php +++ b/src/Generated/Groups/Item/Sites/Item/Onenote/Pages/PagesRequestBuilder.php @@ -52,7 +52,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * The pages in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The pages in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @param PagesRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -81,7 +81,7 @@ public function post(OnenotePage $body, ?PagesRequestBuilderPostRequestConfigura } /** - * The pages in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The pages in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @param PagesRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Groups/Item/Sites/Item/Onenote/Pages/PagesRequestBuilderGetQueryParameters.php b/src/Generated/Groups/Item/Sites/Item/Onenote/Pages/PagesRequestBuilderGetQueryParameters.php index 6a562da9481..bd5e737541c 100644 --- a/src/Generated/Groups/Item/Sites/Item/Onenote/Pages/PagesRequestBuilderGetQueryParameters.php +++ b/src/Generated/Groups/Item/Sites/Item/Onenote/Pages/PagesRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * The pages in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The pages in all OneNote notebooks that the user or group owns. Read-only. Nullable. */ class PagesRequestBuilderGetQueryParameters { diff --git a/src/Generated/Groups/Item/Sites/Item/Onenote/SectionGroups/Item/SectionGroupItemRequestBuilder.php b/src/Generated/Groups/Item/Sites/Item/Onenote/SectionGroups/Item/SectionGroupItemRequestBuilder.php index 4271376a229..ae47f2edf03 100644 --- a/src/Generated/Groups/Item/Sites/Item/Onenote/SectionGroups/Item/SectionGroupItemRequestBuilder.php +++ b/src/Generated/Groups/Item/Sites/Item/Onenote/SectionGroups/Item/SectionGroupItemRequestBuilder.php @@ -77,7 +77,7 @@ public function delete(?SectionGroupItemRequestBuilderDeleteRequestConfiguration } /** - * The section groups in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The section groups in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @param SectionGroupItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -124,7 +124,7 @@ public function toDeleteRequestInformation(?SectionGroupItemRequestBuilderDelete } /** - * The section groups in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The section groups in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @param SectionGroupItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Groups/Item/Sites/Item/Onenote/SectionGroups/Item/SectionGroupItemRequestBuilderGetQueryParameters.php b/src/Generated/Groups/Item/Sites/Item/Onenote/SectionGroups/Item/SectionGroupItemRequestBuilderGetQueryParameters.php index a0432c2b2a4..342d1453841 100644 --- a/src/Generated/Groups/Item/Sites/Item/Onenote/SectionGroups/Item/SectionGroupItemRequestBuilderGetQueryParameters.php +++ b/src/Generated/Groups/Item/Sites/Item/Onenote/SectionGroups/Item/SectionGroupItemRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * The section groups in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The section groups in all OneNote notebooks that the user or group owns. Read-only. Nullable. */ class SectionGroupItemRequestBuilderGetQueryParameters { diff --git a/src/Generated/Groups/Item/Sites/Item/Onenote/SectionGroups/SectionGroupsRequestBuilder.php b/src/Generated/Groups/Item/Sites/Item/Onenote/SectionGroups/SectionGroupsRequestBuilder.php index 7b1f0d542e5..3feeb28c940 100644 --- a/src/Generated/Groups/Item/Sites/Item/Onenote/SectionGroups/SectionGroupsRequestBuilder.php +++ b/src/Generated/Groups/Item/Sites/Item/Onenote/SectionGroups/SectionGroupsRequestBuilder.php @@ -52,7 +52,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * The section groups in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The section groups in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @param SectionGroupsRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -81,7 +81,7 @@ public function post(SectionGroup $body, ?SectionGroupsRequestBuilderPostRequest } /** - * The section groups in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The section groups in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @param SectionGroupsRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Groups/Item/Sites/Item/Onenote/SectionGroups/SectionGroupsRequestBuilderGetQueryParameters.php b/src/Generated/Groups/Item/Sites/Item/Onenote/SectionGroups/SectionGroupsRequestBuilderGetQueryParameters.php index 063c889f998..cac0ffd656d 100644 --- a/src/Generated/Groups/Item/Sites/Item/Onenote/SectionGroups/SectionGroupsRequestBuilderGetQueryParameters.php +++ b/src/Generated/Groups/Item/Sites/Item/Onenote/SectionGroups/SectionGroupsRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * The section groups in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The section groups in all OneNote notebooks that the user or group owns. Read-only. Nullable. */ class SectionGroupsRequestBuilderGetQueryParameters { diff --git a/src/Generated/Groups/Item/Sites/Item/Onenote/Sections/Item/OnenoteSectionItemRequestBuilder.php b/src/Generated/Groups/Item/Sites/Item/Onenote/Sections/Item/OnenoteSectionItemRequestBuilder.php index f643737ce09..62c2c5448f1 100644 --- a/src/Generated/Groups/Item/Sites/Item/Onenote/Sections/Item/OnenoteSectionItemRequestBuilder.php +++ b/src/Generated/Groups/Item/Sites/Item/Onenote/Sections/Item/OnenoteSectionItemRequestBuilder.php @@ -85,7 +85,7 @@ public function delete(?OnenoteSectionItemRequestBuilderDeleteRequestConfigurati } /** - * The sections in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The sections in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @param OnenoteSectionItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -132,7 +132,7 @@ public function toDeleteRequestInformation(?OnenoteSectionItemRequestBuilderDele } /** - * The sections in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The sections in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @param OnenoteSectionItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Groups/Item/Sites/Item/Onenote/Sections/Item/OnenoteSectionItemRequestBuilderGetQueryParameters.php b/src/Generated/Groups/Item/Sites/Item/Onenote/Sections/Item/OnenoteSectionItemRequestBuilderGetQueryParameters.php index e39c823120b..5a716c56abc 100644 --- a/src/Generated/Groups/Item/Sites/Item/Onenote/Sections/Item/OnenoteSectionItemRequestBuilderGetQueryParameters.php +++ b/src/Generated/Groups/Item/Sites/Item/Onenote/Sections/Item/OnenoteSectionItemRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * The sections in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The sections in all OneNote notebooks that the user or group owns. Read-only. Nullable. */ class OnenoteSectionItemRequestBuilderGetQueryParameters { diff --git a/src/Generated/Groups/Item/Sites/Item/Onenote/Sections/SectionsRequestBuilder.php b/src/Generated/Groups/Item/Sites/Item/Onenote/Sections/SectionsRequestBuilder.php index b043a091a17..d86f592ed81 100644 --- a/src/Generated/Groups/Item/Sites/Item/Onenote/Sections/SectionsRequestBuilder.php +++ b/src/Generated/Groups/Item/Sites/Item/Onenote/Sections/SectionsRequestBuilder.php @@ -52,7 +52,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * The sections in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The sections in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @param SectionsRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -81,7 +81,7 @@ public function post(OnenoteSection $body, ?SectionsRequestBuilderPostRequestCon } /** - * The sections in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The sections in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @param SectionsRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Groups/Item/Sites/Item/Onenote/Sections/SectionsRequestBuilderGetQueryParameters.php b/src/Generated/Groups/Item/Sites/Item/Onenote/Sections/SectionsRequestBuilderGetQueryParameters.php index 8276dd4a132..2e076e49d7d 100644 --- a/src/Generated/Groups/Item/Sites/Item/Onenote/Sections/SectionsRequestBuilderGetQueryParameters.php +++ b/src/Generated/Groups/Item/Sites/Item/Onenote/Sections/SectionsRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * The sections in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The sections in all OneNote notebooks that the user or group owns. Read-only. Nullable. */ class SectionsRequestBuilderGetQueryParameters { diff --git a/src/Generated/Groups/Item/Threads/Item/Reply/ReplyRequestBuilder.php b/src/Generated/Groups/Item/Threads/Item/Reply/ReplyRequestBuilder.php index 14ea330a960..7864e9d8a17 100644 --- a/src/Generated/Groups/Item/Threads/Item/Reply/ReplyRequestBuilder.php +++ b/src/Generated/Groups/Item/Threads/Item/Reply/ReplyRequestBuilder.php @@ -30,12 +30,12 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Create an open extension (openTypeExtension object) and add custom properties in a new or existing instance of a resource. You can create an open extension in a resource instance and store custom data to it all in the same operation, except for specific resources. The table in the Permissions section lists the resources that support open extensions. + * Reply to a post and add a new post to the specified thread in a group conversation. You can specify both the parent conversation and thread in the request, or, you can specify just the parent thread without the parent conversation. * @param ReplyPostRequestBody $body The request body * @param ReplyRequestBuilderPostRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception - * @link https://learn.microsoft.com/graph/api/opentypeextension-post-opentypeextension?view=graph-rest-beta Find more info here + * @link https://learn.microsoft.com/graph/api/post-reply?view=graph-rest-beta Find more info here */ public function post(ReplyPostRequestBody $body, ?ReplyRequestBuilderPostRequestConfiguration $requestConfiguration = null): Promise { $requestInfo = $this->toPostRequestInformation($body, $requestConfiguration); @@ -46,7 +46,7 @@ public function post(ReplyPostRequestBody $body, ?ReplyRequestBuilderPostRequest } /** - * Create an open extension (openTypeExtension object) and add custom properties in a new or existing instance of a resource. You can create an open extension in a resource instance and store custom data to it all in the same operation, except for specific resources. The table in the Permissions section lists the resources that support open extensions. + * Reply to a post and add a new post to the specified thread in a group conversation. You can specify both the parent conversation and thread in the request, or, you can specify just the parent thread without the parent conversation. * @param ReplyPostRequestBody $body The request body * @param ReplyRequestBuilderPostRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation diff --git a/src/Generated/Identity/ConditionalAccess/NamedLocations/Item/NamedLocationItemRequestBuilder.php b/src/Generated/Identity/ConditionalAccess/NamedLocations/Item/NamedLocationItemRequestBuilder.php index f5793d76de4..b4cbc44eec3 100644 --- a/src/Generated/Identity/ConditionalAccess/NamedLocations/Item/NamedLocationItemRequestBuilder.php +++ b/src/Generated/Identity/ConditionalAccess/NamedLocations/Item/NamedLocationItemRequestBuilder.php @@ -61,12 +61,12 @@ public function get(?NamedLocationItemRequestBuilderGetRequestConfiguration $req } /** - * Update the properties of a countryNamedLocation object. + * Update the properties of an ipNamedLocation object. * @param NamedLocation $body The request body * @param NamedLocationItemRequestBuilderPatchRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception - * @link https://learn.microsoft.com/graph/api/countrynamedlocation-update?view=graph-rest-beta Find more info here + * @link https://learn.microsoft.com/graph/api/ipnamedlocation-update?view=graph-rest-beta Find more info here */ public function patch(NamedLocation $body, ?NamedLocationItemRequestBuilderPatchRequestConfiguration $requestConfiguration = null): Promise { $requestInfo = $this->toPatchRequestInformation($body, $requestConfiguration); @@ -116,7 +116,7 @@ public function toGetRequestInformation(?NamedLocationItemRequestBuilderGetReque } /** - * Update the properties of a countryNamedLocation object. + * Update the properties of an ipNamedLocation object. * @param NamedLocation $body The request body * @param NamedLocationItemRequestBuilderPatchRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation diff --git a/src/Generated/IdentityGovernance/EntitlementManagement/AccessPackageCatalogs/Item/AccessPackageCustomWorkflowExtensions/Item/CustomCalloutExtensionItemRequestBuilder.php b/src/Generated/IdentityGovernance/EntitlementManagement/AccessPackageCatalogs/Item/AccessPackageCustomWorkflowExtensions/Item/CustomCalloutExtensionItemRequestBuilder.php index 99752890f7a..290cf013281 100644 --- a/src/Generated/IdentityGovernance/EntitlementManagement/AccessPackageCatalogs/Item/AccessPackageCustomWorkflowExtensions/Item/CustomCalloutExtensionItemRequestBuilder.php +++ b/src/Generated/IdentityGovernance/EntitlementManagement/AccessPackageCatalogs/Item/AccessPackageCustomWorkflowExtensions/Item/CustomCalloutExtensionItemRequestBuilder.php @@ -45,11 +45,11 @@ public function delete(?CustomCalloutExtensionItemRequestBuilderDeleteRequestCon } /** - * Read the properties and relationships of an accessPackageAssignmentWorkflowExtension object. + * Read the properties and relationships of an accessPackageAssignmentRequestWorkflowExtension object. * @param CustomCalloutExtensionItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception - * @link https://learn.microsoft.com/graph/api/accesspackageassignmentworkflowextension-get?view=graph-rest-beta Find more info here + * @link https://learn.microsoft.com/graph/api/accesspackageassignmentrequestworkflowextension-get?view=graph-rest-beta Find more info here */ public function get(?CustomCalloutExtensionItemRequestBuilderGetRequestConfiguration $requestConfiguration = null): Promise { $requestInfo = $this->toGetRequestInformation($requestConfiguration); @@ -94,7 +94,7 @@ public function toDeleteRequestInformation(?CustomCalloutExtensionItemRequestBui } /** - * Read the properties and relationships of an accessPackageAssignmentWorkflowExtension object. + * Read the properties and relationships of an accessPackageAssignmentRequestWorkflowExtension object. * @param CustomCalloutExtensionItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/IdentityGovernance/EntitlementManagement/AccessPackageCatalogs/Item/AccessPackageCustomWorkflowExtensions/Item/CustomCalloutExtensionItemRequestBuilderGetQueryParameters.php b/src/Generated/IdentityGovernance/EntitlementManagement/AccessPackageCatalogs/Item/AccessPackageCustomWorkflowExtensions/Item/CustomCalloutExtensionItemRequestBuilderGetQueryParameters.php index c63948e8ae2..0c3bbf4d14d 100644 --- a/src/Generated/IdentityGovernance/EntitlementManagement/AccessPackageCatalogs/Item/AccessPackageCustomWorkflowExtensions/Item/CustomCalloutExtensionItemRequestBuilderGetQueryParameters.php +++ b/src/Generated/IdentityGovernance/EntitlementManagement/AccessPackageCatalogs/Item/AccessPackageCustomWorkflowExtensions/Item/CustomCalloutExtensionItemRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Read the properties and relationships of an accessPackageAssignmentWorkflowExtension object. + * Read the properties and relationships of an accessPackageAssignmentRequestWorkflowExtension object. */ class CustomCalloutExtensionItemRequestBuilderGetQueryParameters { diff --git a/src/Generated/IdentityGovernance/EntitlementManagement/AccessPackageCatalogs/Item/CustomAccessPackageWorkflowExtensions/Item/CustomAccessPackageWorkflowExtensionItemRequestBuilder.php b/src/Generated/IdentityGovernance/EntitlementManagement/AccessPackageCatalogs/Item/CustomAccessPackageWorkflowExtensions/Item/CustomAccessPackageWorkflowExtensionItemRequestBuilder.php index 973cd307015..6b91fa3ead3 100644 --- a/src/Generated/IdentityGovernance/EntitlementManagement/AccessPackageCatalogs/Item/CustomAccessPackageWorkflowExtensions/Item/CustomAccessPackageWorkflowExtensionItemRequestBuilder.php +++ b/src/Generated/IdentityGovernance/EntitlementManagement/AccessPackageCatalogs/Item/CustomAccessPackageWorkflowExtensions/Item/CustomAccessPackageWorkflowExtensionItemRequestBuilder.php @@ -31,11 +31,11 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Delete an accessPackageAssignmentRequestWorkflowExtension object. The custom workflow extension must first be removed from any associated policies before it can be deleted. Follow these steps to remove the custom workflow extension from any associated policies:1. First retrieve the accessPackageCatalogId by calling the Get accessPackageAssignmentPolicies operation and appending ?$expand=accessPackage($expand=accessPackageCatalog) to the query. For example, https://graph.microsoft.com/beta/identityGovernance/entitlementManagement/accessPackageAssignmentPolicies?$expand=accessPackage($expand=accessPackageCatalog).2. Use the access package catalog ID and retrieve the ID of the accessPackageCustomWorkflowExtension object that you want to delete by running the List accessPackageCustomWorkflowExtensions operation.3. Call the Update accessPackageAssignmentPolicy operation to remove the custom workflow extension object from the policy. For an example, see Example 3: Remove the customExtensionStageSettings from a policy. + * Delete a customAccessPackageWorkflowExtension object. The custom workflow extension must first be removed from any associated policies before it can be deleted. Follow these steps to remove the custom workflow extension from any associated policies:1. First retrieve the accessPackageCatalogId by calling the Get accessPackageAssignmentPolicies operation and appending ?$expand=accessPackage($expand=accessPackageCatalog) to the query. For example, https://graph.microsoft.com/beta/identityGovernance/entitlementManagement/accessPackageAssignmentPolicies?$expand=accessPackage($expand=accessPackageCatalog).2. Use the access package catalog ID and retrieve the ID of the customAccessPackageWorkflowExtension object that you want to delete by running the LIST customAccessPackageWorkflowExtensions operation.3. Call the Update accessPackageAssignmentPolicy operation to remove the custom workflow extension object from the policy. For an example, see Example 2: Remove the customExtensionHandlers and verifiableCredentialSettings from a policy. * @param CustomAccessPackageWorkflowExtensionItemRequestBuilderDeleteRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception - * @link https://learn.microsoft.com/graph/api/accesspackageassignmentrequestworkflowextension-delete?view=graph-rest-beta Find more info here + * @link https://learn.microsoft.com/graph/api/customaccesspackageworkflowextension-delete?view=graph-rest-beta Find more info here */ public function delete(?CustomAccessPackageWorkflowExtensionItemRequestBuilderDeleteRequestConfiguration $requestConfiguration = null): Promise { $requestInfo = $this->toDeleteRequestInformation($requestConfiguration); @@ -77,7 +77,7 @@ public function patch(CustomAccessPackageWorkflowExtension $body, ?CustomAccessP } /** - * Delete an accessPackageAssignmentRequestWorkflowExtension object. The custom workflow extension must first be removed from any associated policies before it can be deleted. Follow these steps to remove the custom workflow extension from any associated policies:1. First retrieve the accessPackageCatalogId by calling the Get accessPackageAssignmentPolicies operation and appending ?$expand=accessPackage($expand=accessPackageCatalog) to the query. For example, https://graph.microsoft.com/beta/identityGovernance/entitlementManagement/accessPackageAssignmentPolicies?$expand=accessPackage($expand=accessPackageCatalog).2. Use the access package catalog ID and retrieve the ID of the accessPackageCustomWorkflowExtension object that you want to delete by running the List accessPackageCustomWorkflowExtensions operation.3. Call the Update accessPackageAssignmentPolicy operation to remove the custom workflow extension object from the policy. For an example, see Example 3: Remove the customExtensionStageSettings from a policy. + * Delete a customAccessPackageWorkflowExtension object. The custom workflow extension must first be removed from any associated policies before it can be deleted. Follow these steps to remove the custom workflow extension from any associated policies:1. First retrieve the accessPackageCatalogId by calling the Get accessPackageAssignmentPolicies operation and appending ?$expand=accessPackage($expand=accessPackageCatalog) to the query. For example, https://graph.microsoft.com/beta/identityGovernance/entitlementManagement/accessPackageAssignmentPolicies?$expand=accessPackage($expand=accessPackageCatalog).2. Use the access package catalog ID and retrieve the ID of the customAccessPackageWorkflowExtension object that you want to delete by running the LIST customAccessPackageWorkflowExtensions operation.3. Call the Update accessPackageAssignmentPolicy operation to remove the custom workflow extension object from the policy. For an example, see Example 2: Remove the customExtensionHandlers and verifiableCredentialSettings from a policy. * @param CustomAccessPackageWorkflowExtensionItemRequestBuilderDeleteRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/IdentityGovernance/EntitlementManagement/AccessPackages/Item/AccessPackageItemRequestBuilder.php b/src/Generated/IdentityGovernance/EntitlementManagement/AccessPackages/Item/AccessPackageItemRequestBuilder.php index 0b3bfdc136d..24b59152a99 100644 --- a/src/Generated/IdentityGovernance/EntitlementManagement/AccessPackages/Item/AccessPackageItemRequestBuilder.php +++ b/src/Generated/IdentityGovernance/EntitlementManagement/AccessPackages/Item/AccessPackageItemRequestBuilder.php @@ -120,11 +120,11 @@ public function delete(?AccessPackageItemRequestBuilderDeleteRequestConfiguratio } /** - * Retrieve an access package with a list of accessPackageResourceRoleScope objects. These objects represent the resource roles that an access package assigns to each subject. Each object links to an accessPackageResourceRole and an accessPackageResourceScope. + * Retrieve the properties and relationships of an accessPackage object. * @param AccessPackageItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception - * @link https://learn.microsoft.com/graph/api/accesspackage-list-accesspackageresourcerolescopes?view=graph-rest-beta Find more info here + * @link https://learn.microsoft.com/graph/api/accesspackage-get?view=graph-rest-beta Find more info here */ public function get(?AccessPackageItemRequestBuilderGetRequestConfiguration $requestConfiguration = null): Promise { $requestInfo = $this->toGetRequestInformation($requestConfiguration); @@ -169,7 +169,7 @@ public function toDeleteRequestInformation(?AccessPackageItemRequestBuilderDelet } /** - * Retrieve an access package with a list of accessPackageResourceRoleScope objects. These objects represent the resource roles that an access package assigns to each subject. Each object links to an accessPackageResourceRole and an accessPackageResourceScope. + * Retrieve the properties and relationships of an accessPackage object. * @param AccessPackageItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/IdentityGovernance/EntitlementManagement/AccessPackages/Item/AccessPackageItemRequestBuilderGetQueryParameters.php b/src/Generated/IdentityGovernance/EntitlementManagement/AccessPackages/Item/AccessPackageItemRequestBuilderGetQueryParameters.php index b1ff43ca6d4..b2fe7f6b346 100644 --- a/src/Generated/IdentityGovernance/EntitlementManagement/AccessPackages/Item/AccessPackageItemRequestBuilderGetQueryParameters.php +++ b/src/Generated/IdentityGovernance/EntitlementManagement/AccessPackages/Item/AccessPackageItemRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Retrieve an access package with a list of accessPackageResourceRoleScope objects. These objects represent the resource roles that an access package assigns to each subject. Each object links to an accessPackageResourceRole and an accessPackageResourceScope. + * Retrieve the properties and relationships of an accessPackage object. */ class AccessPackageItemRequestBuilderGetQueryParameters { diff --git a/src/Generated/IdentityGovernance/EntitlementManagement/AccessPackagesWithUniqueName/AccessPackagesWithUniqueNameRequestBuilder.php b/src/Generated/IdentityGovernance/EntitlementManagement/AccessPackagesWithUniqueName/AccessPackagesWithUniqueNameRequestBuilder.php index 4ec0ae29611..c463b1c09aa 100644 --- a/src/Generated/IdentityGovernance/EntitlementManagement/AccessPackagesWithUniqueName/AccessPackagesWithUniqueNameRequestBuilder.php +++ b/src/Generated/IdentityGovernance/EntitlementManagement/AccessPackagesWithUniqueName/AccessPackagesWithUniqueNameRequestBuilder.php @@ -65,11 +65,11 @@ public function delete(?AccessPackagesWithUniqueNameRequestBuilderDeleteRequestC } /** - * Retrieve an access package with a list of accessPackageResourceRoleScope objects. These objects represent the resource roles that an access package assigns to each subject. Each object links to an accessPackageResourceRole and an accessPackageResourceScope. + * Retrieve the properties and relationships of an accessPackage object. * @param AccessPackagesWithUniqueNameRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception - * @link https://learn.microsoft.com/graph/api/accesspackage-list-accesspackageresourcerolescopes?view=graph-rest-beta Find more info here + * @link https://learn.microsoft.com/graph/api/accesspackage-get?view=graph-rest-beta Find more info here */ public function get(?AccessPackagesWithUniqueNameRequestBuilderGetRequestConfiguration $requestConfiguration = null): Promise { $requestInfo = $this->toGetRequestInformation($requestConfiguration); @@ -114,7 +114,7 @@ public function toDeleteRequestInformation(?AccessPackagesWithUniqueNameRequestB } /** - * Retrieve an access package with a list of accessPackageResourceRoleScope objects. These objects represent the resource roles that an access package assigns to each subject. Each object links to an accessPackageResourceRole and an accessPackageResourceScope. + * Retrieve the properties and relationships of an accessPackage object. * @param AccessPackagesWithUniqueNameRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/IdentityGovernance/EntitlementManagement/AccessPackagesWithUniqueName/AccessPackagesWithUniqueNameRequestBuilderGetQueryParameters.php b/src/Generated/IdentityGovernance/EntitlementManagement/AccessPackagesWithUniqueName/AccessPackagesWithUniqueNameRequestBuilderGetQueryParameters.php index 62a3fe523c2..8900e6f934e 100644 --- a/src/Generated/IdentityGovernance/EntitlementManagement/AccessPackagesWithUniqueName/AccessPackagesWithUniqueNameRequestBuilderGetQueryParameters.php +++ b/src/Generated/IdentityGovernance/EntitlementManagement/AccessPackagesWithUniqueName/AccessPackagesWithUniqueNameRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Retrieve an access package with a list of accessPackageResourceRoleScope objects. These objects represent the resource roles that an access package assigns to each subject. Each object links to an accessPackageResourceRole and an accessPackageResourceScope. + * Retrieve the properties and relationships of an accessPackage object. */ class AccessPackagesWithUniqueNameRequestBuilderGetQueryParameters { diff --git a/src/Generated/IdentityGovernance/TermsOfUse/Agreements/Item/AgreementItemRequestBuilder.php b/src/Generated/IdentityGovernance/TermsOfUse/Agreements/Item/AgreementItemRequestBuilder.php index 00d359b13d3..69b1ac60dbc 100644 --- a/src/Generated/IdentityGovernance/TermsOfUse/Agreements/Item/AgreementItemRequestBuilder.php +++ b/src/Generated/IdentityGovernance/TermsOfUse/Agreements/Item/AgreementItemRequestBuilder.php @@ -70,11 +70,11 @@ public function delete(?AgreementItemRequestBuilderDeleteRequestConfiguration $r } /** - * Retrieve the properties and relationships of an agreement object. + * Retrieve all files related to an agreement. This includes the default file and all localized files. * @param AgreementItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception - * @link https://learn.microsoft.com/graph/api/agreement-get?view=graph-rest-beta Find more info here + * @link https://learn.microsoft.com/graph/api/agreement-list-files?view=graph-rest-beta Find more info here */ public function get(?AgreementItemRequestBuilderGetRequestConfiguration $requestConfiguration = null): Promise { $requestInfo = $this->toGetRequestInformation($requestConfiguration); @@ -119,7 +119,7 @@ public function toDeleteRequestInformation(?AgreementItemRequestBuilderDeleteReq } /** - * Retrieve the properties and relationships of an agreement object. + * Retrieve all files related to an agreement. This includes the default file and all localized files. * @param AgreementItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/IdentityGovernance/TermsOfUse/Agreements/Item/AgreementItemRequestBuilderGetQueryParameters.php b/src/Generated/IdentityGovernance/TermsOfUse/Agreements/Item/AgreementItemRequestBuilderGetQueryParameters.php index e1d6d93093c..08036143775 100644 --- a/src/Generated/IdentityGovernance/TermsOfUse/Agreements/Item/AgreementItemRequestBuilderGetQueryParameters.php +++ b/src/Generated/IdentityGovernance/TermsOfUse/Agreements/Item/AgreementItemRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Retrieve the properties and relationships of an agreement object. + * Retrieve all files related to an agreement. This includes the default file and all localized files. */ class AgreementItemRequestBuilderGetQueryParameters { diff --git a/src/Generated/IdentityProtection/RiskDetections/Item/RiskDetectionItemRequestBuilder.php b/src/Generated/IdentityProtection/RiskDetections/Item/RiskDetectionItemRequestBuilder.php index 7dc8b7c1972..c1f0eaae8a2 100644 --- a/src/Generated/IdentityProtection/RiskDetections/Item/RiskDetectionItemRequestBuilder.php +++ b/src/Generated/IdentityProtection/RiskDetections/Item/RiskDetectionItemRequestBuilder.php @@ -45,11 +45,11 @@ public function delete(?RiskDetectionItemRequestBuilderDeleteRequestConfiguratio } /** - * Retrieve the properties of a riskDetection object. + * Retrieve the properties of a collection of riskDetection objects. * @param RiskDetectionItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception - * @link https://learn.microsoft.com/graph/api/riskdetection-get?view=graph-rest-beta Find more info here + * @link https://learn.microsoft.com/graph/api/riskdetection-list?view=graph-rest-beta Find more info here */ public function get(?RiskDetectionItemRequestBuilderGetRequestConfiguration $requestConfiguration = null): Promise { $requestInfo = $this->toGetRequestInformation($requestConfiguration); @@ -93,7 +93,7 @@ public function toDeleteRequestInformation(?RiskDetectionItemRequestBuilderDelet } /** - * Retrieve the properties of a riskDetection object. + * Retrieve the properties of a collection of riskDetection objects. * @param RiskDetectionItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/IdentityProtection/RiskDetections/Item/RiskDetectionItemRequestBuilderGetQueryParameters.php b/src/Generated/IdentityProtection/RiskDetections/Item/RiskDetectionItemRequestBuilderGetQueryParameters.php index d07753ed90d..0ed3e0e8b9c 100644 --- a/src/Generated/IdentityProtection/RiskDetections/Item/RiskDetectionItemRequestBuilderGetQueryParameters.php +++ b/src/Generated/IdentityProtection/RiskDetections/Item/RiskDetectionItemRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Retrieve the properties of a riskDetection object. + * Retrieve the properties of a collection of riskDetection objects. */ class RiskDetectionItemRequestBuilderGetQueryParameters { diff --git a/src/Generated/Models/AndroidManagedAppProtection.php b/src/Generated/Models/AndroidManagedAppProtection.php index 124a6da69c7..24eec1b46d9 100644 --- a/src/Generated/Models/AndroidManagedAppProtection.php +++ b/src/Generated/Models/AndroidManagedAppProtection.php @@ -240,7 +240,7 @@ public function getConnectToVpnOnLaunch(): ?bool { } /** - * Gets the customBrowserDisplayName property value. Friendly name of the preferred custom browser to open weblink on Android. + * Gets the customBrowserDisplayName property value. Friendly name of the preferred custom browser to open weblink on Android. When this property is configured, ManagedBrowserToOpenLinksRequired should be true. * @return string|null */ public function getCustomBrowserDisplayName(): ?string { @@ -252,7 +252,7 @@ public function getCustomBrowserDisplayName(): ?string { } /** - * Gets the customBrowserPackageId property value. Unique identifier of a custom browser to open weblink on Android. + * Gets the customBrowserPackageId property value. Unique identifier of the preferred custom browser to open weblink on Android. When this property is configured, ManagedBrowserToOpenLinksRequired should be true. * @return string|null */ public function getCustomBrowserPackageId(): ?string { @@ -829,7 +829,7 @@ public function setConnectToVpnOnLaunch(?bool $value): void { } /** - * Sets the customBrowserDisplayName property value. Friendly name of the preferred custom browser to open weblink on Android. + * Sets the customBrowserDisplayName property value. Friendly name of the preferred custom browser to open weblink on Android. When this property is configured, ManagedBrowserToOpenLinksRequired should be true. * @param string|null $value Value to set for the customBrowserDisplayName property. */ public function setCustomBrowserDisplayName(?string $value): void { @@ -837,7 +837,7 @@ public function setCustomBrowserDisplayName(?string $value): void { } /** - * Sets the customBrowserPackageId property value. Unique identifier of a custom browser to open weblink on Android. + * Sets the customBrowserPackageId property value. Unique identifier of the preferred custom browser to open weblink on Android. When this property is configured, ManagedBrowserToOpenLinksRequired should be true. * @param string|null $value Value to set for the customBrowserPackageId property. */ public function setCustomBrowserPackageId(?string $value): void { diff --git a/src/Generated/Models/Authentication.php b/src/Generated/Models/Authentication.php index 05d807d8b08..2398afbbda3 100644 --- a/src/Generated/Models/Authentication.php +++ b/src/Generated/Models/Authentication.php @@ -79,7 +79,7 @@ public function getFieldDeserializers(): array { } /** - * Gets the hardwareOathMethods property value. The hardwareOathMethods property + * Gets the hardwareOathMethods property value. The hardware OATH time-based one-time password (TOTP) devices assigned to a user for authentication. * @return array|null */ public function getHardwareOathMethods(): ?array { @@ -296,7 +296,7 @@ public function setFido2Methods(?array $value): void { } /** - * Sets the hardwareOathMethods property value. The hardwareOathMethods property + * Sets the hardwareOathMethods property value. The hardware OATH time-based one-time password (TOTP) devices assigned to a user for authentication. * @param array|null $value Value to set for the hardwareOathMethods property. */ public function setHardwareOathMethods(?array $value): void { diff --git a/src/Generated/Models/AuthenticationMethodDevice.php b/src/Generated/Models/AuthenticationMethodDevice.php index 58aac535264..61563707d1d 100644 --- a/src/Generated/Models/AuthenticationMethodDevice.php +++ b/src/Generated/Models/AuthenticationMethodDevice.php @@ -33,7 +33,7 @@ public static function createFromDiscriminatorValue(ParseNode $parseNode): Authe } /** - * Gets the displayName property value. The displayName property + * Gets the displayName property value. Optional name given to the hardware OATH device. * @return string|null */ public function getDisplayName(): ?string { @@ -57,7 +57,7 @@ public function getFieldDeserializers(): array { } /** - * Gets the hardwareOathDevices property value. The hardwareOathDevices property + * Gets the hardwareOathDevices property value. Exposes the hardware OATH method in the directory. * @return array|null */ public function getHardwareOathDevices(): ?array { @@ -81,7 +81,7 @@ public function serialize(SerializationWriter $writer): void { } /** - * Sets the displayName property value. The displayName property + * Sets the displayName property value. Optional name given to the hardware OATH device. * @param string|null $value Value to set for the displayName property. */ public function setDisplayName(?string $value): void { @@ -89,7 +89,7 @@ public function setDisplayName(?string $value): void { } /** - * Sets the hardwareOathDevices property value. The hardwareOathDevices property + * Sets the hardwareOathDevices property value. Exposes the hardware OATH method in the directory. * @param array|null $value Value to set for the hardwareOathDevices property. */ public function setHardwareOathDevices(?array $value): void { diff --git a/src/Generated/Models/BaseSitePage.php b/src/Generated/Models/BaseSitePage.php index 811c58a6951..68e358a70dd 100644 --- a/src/Generated/Models/BaseSitePage.php +++ b/src/Generated/Models/BaseSitePage.php @@ -49,7 +49,7 @@ public function getFieldDeserializers(): array { } /** - * Gets the pageLayout property value. The name of the page layout of the page. The possible values are: microsoftReserved, article, home, unknownFutureValue. + * Gets the pageLayout property value. The name of the page layout of the page. The possible values are: microsoftReserved, article, home, unknownFutureValue, newsLink. You must use the Prefer: include-unknown-enum-members request header to get the following value in this evolvable enum: newsLink. * @return PageLayoutType|null */ public function getPageLayout(): ?PageLayoutType { @@ -96,7 +96,7 @@ public function serialize(SerializationWriter $writer): void { } /** - * Sets the pageLayout property value. The name of the page layout of the page. The possible values are: microsoftReserved, article, home, unknownFutureValue. + * Sets the pageLayout property value. The name of the page layout of the page. The possible values are: microsoftReserved, article, home, unknownFutureValue, newsLink. You must use the Prefer: include-unknown-enum-members request header to get the following value in this evolvable enum: newsLink. * @param PageLayoutType|null $value Value to set for the pageLayout property. */ public function setPageLayout(?PageLayoutType $value): void { diff --git a/src/Generated/Models/CloudPcCrossRegionDisasterRecoverySetting.php b/src/Generated/Models/CloudPcCrossRegionDisasterRecoverySetting.php index 23d5a258b6a..d1553095aea 100644 --- a/src/Generated/Models/CloudPcCrossRegionDisasterRecoverySetting.php +++ b/src/Generated/Models/CloudPcCrossRegionDisasterRecoverySetting.php @@ -56,7 +56,7 @@ public function getBackingStore(): BackingStore { } /** - * Gets the crossRegionDisasterRecoveryEnabled property value. True if an end user is allowed to set up cross-region disaster recovery for Cloud PC; otherwise, false. The default value is false. + * Gets the crossRegionDisasterRecoveryEnabled property value. True if an end user is allowed to set up cross-region disaster recovery for Cloud PC; otherwise, false. The default value is false. This property is deprecated and will no longer be supported effective February 11, 2025. For scenarios where crossRegionDisasterRecoveryEnabled is true, set disasterRecoveryType to crossRegion. For scenarios where crossRegionDisasterRecoveryEnabled is false, set disasterRecoveryType to notconfigured. * @return bool|null */ public function getCrossRegionDisasterRecoveryEnabled(): ?bool { @@ -80,7 +80,7 @@ public function getDisasterRecoveryNetworkSetting(): ?CloudPcDisasterRecoveryNet } /** - * Gets the disasterRecoveryType property value. The disasterRecoveryType property + * Gets the disasterRecoveryType property value. Indicates the type of disaster recovery to perform when a disaster occurs on the user's Cloud PC. The possible values are: notConfigured, crossRegion, premium, unknownFutureValue. The default value is notConfigured. * @return CloudPcDisasterRecoveryType|null */ public function getDisasterRecoveryType(): ?CloudPcDisasterRecoveryType { @@ -160,7 +160,7 @@ public function setBackingStore(BackingStore $value): void { } /** - * Sets the crossRegionDisasterRecoveryEnabled property value. True if an end user is allowed to set up cross-region disaster recovery for Cloud PC; otherwise, false. The default value is false. + * Sets the crossRegionDisasterRecoveryEnabled property value. True if an end user is allowed to set up cross-region disaster recovery for Cloud PC; otherwise, false. The default value is false. This property is deprecated and will no longer be supported effective February 11, 2025. For scenarios where crossRegionDisasterRecoveryEnabled is true, set disasterRecoveryType to crossRegion. For scenarios where crossRegionDisasterRecoveryEnabled is false, set disasterRecoveryType to notconfigured. * @param bool|null $value Value to set for the crossRegionDisasterRecoveryEnabled property. */ public function setCrossRegionDisasterRecoveryEnabled(?bool $value): void { @@ -176,7 +176,7 @@ public function setDisasterRecoveryNetworkSetting(?CloudPcDisasterRecoveryNetwor } /** - * Sets the disasterRecoveryType property value. The disasterRecoveryType property + * Sets the disasterRecoveryType property value. Indicates the type of disaster recovery to perform when a disaster occurs on the user's Cloud PC. The possible values are: notConfigured, crossRegion, premium, unknownFutureValue. The default value is notConfigured. * @param CloudPcDisasterRecoveryType|null $value Value to set for the disasterRecoveryType property. */ public function setDisasterRecoveryType(?CloudPcDisasterRecoveryType $value): void { diff --git a/src/Generated/Models/DeviceCompliancePolicy.php b/src/Generated/Models/DeviceCompliancePolicy.php index 74baec07ed6..7a96a798370 100644 --- a/src/Generated/Models/DeviceCompliancePolicy.php +++ b/src/Generated/Models/DeviceCompliancePolicy.php @@ -194,7 +194,7 @@ public function getRoleScopeTagIds(): ?array { } /** - * Gets the scheduledActionsForRule property value. The list of scheduled action for this rule + * Gets the scheduledActionsForRule property value. The list of scheduled action per rule for this compliance policy. This is a required property when creating any individual per-platform compliance policies. * @return array|null */ public function getScheduledActionsForRule(): ?array { @@ -339,7 +339,7 @@ public function setRoleScopeTagIds(?array $value): void { } /** - * Sets the scheduledActionsForRule property value. The list of scheduled action for this rule + * Sets the scheduledActionsForRule property value. The list of scheduled action per rule for this compliance policy. This is a required property when creating any individual per-platform compliance policies. * @param array|null $value Value to set for the scheduledActionsForRule property. */ public function setScheduledActionsForRule(?array $value): void { diff --git a/src/Generated/Models/DeviceManagementConfigurationChoiceSettingDefinition.php b/src/Generated/Models/DeviceManagementConfigurationChoiceSettingDefinition.php index fac8e0db529..7b76a170b98 100644 --- a/src/Generated/Models/DeviceManagementConfigurationChoiceSettingDefinition.php +++ b/src/Generated/Models/DeviceManagementConfigurationChoiceSettingDefinition.php @@ -33,7 +33,7 @@ public static function createFromDiscriminatorValue(ParseNode $parseNode): Devic } /** - * Gets the defaultOptionId property value. Default option for the choice setting. + * Gets the defaultOptionId property value. Default option for choice setting * @return string|null */ public function getDefaultOptionId(): ?string { @@ -57,7 +57,7 @@ public function getFieldDeserializers(): array { } /** - * Gets the options property value. Options for the setting that can be selected. + * Gets the options property value. Options for the setting that can be selected * @return array|null */ public function getOptions(): ?array { @@ -81,7 +81,7 @@ public function serialize(SerializationWriter $writer): void { } /** - * Sets the defaultOptionId property value. Default option for the choice setting. + * Sets the defaultOptionId property value. Default option for choice setting * @param string|null $value Value to set for the defaultOptionId property. */ public function setDefaultOptionId(?string $value): void { @@ -89,7 +89,7 @@ public function setDefaultOptionId(?string $value): void { } /** - * Sets the options property value. Options for the setting that can be selected. + * Sets the options property value. Options for the setting that can be selected * @param array|null $value Value to set for the options property. */ public function setOptions(?array $value): void { diff --git a/src/Generated/Models/DeviceManagementConfigurationReferredSettingInformation.php b/src/Generated/Models/DeviceManagementConfigurationReferredSettingInformation.php index 67276ec05b5..92534302123 100644 --- a/src/Generated/Models/DeviceManagementConfigurationReferredSettingInformation.php +++ b/src/Generated/Models/DeviceManagementConfigurationReferredSettingInformation.php @@ -83,7 +83,7 @@ public function getOdataType(): ?string { } /** - * Gets the settingDefinitionId property value. Setting definition id that is being referred to a setting. Applicable for reusable setting. + * Gets the settingDefinitionId property value. Setting definition id that is being referred to a setting. Applicable for reusable setting * @return string|null */ public function getSettingDefinitionId(): ?string { @@ -129,7 +129,7 @@ public function setOdataType(?string $value): void { } /** - * Sets the settingDefinitionId property value. Setting definition id that is being referred to a setting. Applicable for reusable setting. + * Sets the settingDefinitionId property value. Setting definition id that is being referred to a setting. Applicable for reusable setting * @param string|null $value Value to set for the settingDefinitionId property. */ public function setSettingDefinitionId(?string $value): void { diff --git a/src/Generated/Models/DeviceManagementConfigurationSettingGroupCollectionDefinition.php b/src/Generated/Models/DeviceManagementConfigurationSettingGroupCollectionDefinition.php index 8383e8d0b09..92dda4cd8fa 100644 --- a/src/Generated/Models/DeviceManagementConfigurationSettingGroupCollectionDefinition.php +++ b/src/Generated/Models/DeviceManagementConfigurationSettingGroupCollectionDefinition.php @@ -37,7 +37,7 @@ public function getFieldDeserializers(): array { } /** - * Gets the maximumCount property value. Maximum number of setting group count in the collection. Valid values 1 to 100 + * Gets the maximumCount property value. Maximum number of setting group count in the collection * @return int|null */ public function getMaximumCount(): ?int { @@ -49,7 +49,7 @@ public function getMaximumCount(): ?int { } /** - * Gets the minimumCount property value. Minimum number of setting group count in the collection. Valid values 1 to 100 + * Gets the minimumCount property value. Minimum number of setting group count in the collection * @return int|null */ public function getMinimumCount(): ?int { @@ -71,7 +71,7 @@ public function serialize(SerializationWriter $writer): void { } /** - * Sets the maximumCount property value. Maximum number of setting group count in the collection. Valid values 1 to 100 + * Sets the maximumCount property value. Maximum number of setting group count in the collection * @param int|null $value Value to set for the maximumCount property. */ public function setMaximumCount(?int $value): void { @@ -79,7 +79,7 @@ public function setMaximumCount(?int $value): void { } /** - * Sets the minimumCount property value. Minimum number of setting group count in the collection. Valid values 1 to 100 + * Sets the minimumCount property value. Minimum number of setting group count in the collection * @param int|null $value Value to set for the minimumCount property. */ public function setMinimumCount(?int $value): void { diff --git a/src/Generated/Models/DeviceManagementConfigurationSettingGroupDefinition.php b/src/Generated/Models/DeviceManagementConfigurationSettingGroupDefinition.php index 02e1aa77fc4..982aa240d1d 100644 --- a/src/Generated/Models/DeviceManagementConfigurationSettingGroupDefinition.php +++ b/src/Generated/Models/DeviceManagementConfigurationSettingGroupDefinition.php @@ -33,7 +33,7 @@ public static function createFromDiscriminatorValue(ParseNode $parseNode): Devic } /** - * Gets the childIds property value. Dependent child settings to this group of settings + * Gets the childIds property value. Dependent child settings to this group of settings. * @return array|null */ public function getChildIds(): ?array { @@ -106,7 +106,7 @@ public function serialize(SerializationWriter $writer): void { } /** - * Sets the childIds property value. Dependent child settings to this group of settings + * Sets the childIds property value. Dependent child settings to this group of settings. * @param array|null $value Value to set for the childIds property. */ public function setChildIds(?array $value): void { diff --git a/src/Generated/Models/DeviceManagementConfigurationSimpleSettingCollectionDefinition.php b/src/Generated/Models/DeviceManagementConfigurationSimpleSettingCollectionDefinition.php index 2c56f6c957c..8d11d343669 100644 --- a/src/Generated/Models/DeviceManagementConfigurationSimpleSettingCollectionDefinition.php +++ b/src/Generated/Models/DeviceManagementConfigurationSimpleSettingCollectionDefinition.php @@ -37,7 +37,7 @@ public function getFieldDeserializers(): array { } /** - * Gets the maximumCount property value. Maximum number of simple settings in the collection + * Gets the maximumCount property value. Maximum number of simple settings in the collection. Valid values 1 to 100 * @return int|null */ public function getMaximumCount(): ?int { @@ -49,7 +49,7 @@ public function getMaximumCount(): ?int { } /** - * Gets the minimumCount property value. Minimum number of simple settings in the collection + * Gets the minimumCount property value. Minimum number of simple settings in the collection. Valid values 1 to 100 * @return int|null */ public function getMinimumCount(): ?int { @@ -71,7 +71,7 @@ public function serialize(SerializationWriter $writer): void { } /** - * Sets the maximumCount property value. Maximum number of simple settings in the collection + * Sets the maximumCount property value. Maximum number of simple settings in the collection. Valid values 1 to 100 * @param int|null $value Value to set for the maximumCount property. */ public function setMaximumCount(?int $value): void { @@ -79,7 +79,7 @@ public function setMaximumCount(?int $value): void { } /** - * Sets the minimumCount property value. Minimum number of simple settings in the collection + * Sets the minimumCount property value. Minimum number of simple settings in the collection. Valid values 1 to 100 * @param int|null $value Value to set for the minimumCount property. */ public function setMinimumCount(?int $value): void { diff --git a/src/Generated/Models/Directory.php b/src/Generated/Models/Directory.php index 4be80a89d6d..fd1db2329fb 100644 --- a/src/Generated/Models/Directory.php +++ b/src/Generated/Models/Directory.php @@ -54,7 +54,7 @@ public function getAttributeSets(): ?array { } /** - * Gets the authenticationMethodDevices property value. The authenticationMethodDevices property + * Gets the authenticationMethodDevices property value. Exposes the hardware OATH method in the directory. * @return AuthenticationMethodDevice|null */ public function getAuthenticationMethodDevices(): ?AuthenticationMethodDevice { @@ -358,7 +358,7 @@ public function setAttributeSets(?array $value): void { } /** - * Sets the authenticationMethodDevices property value. The authenticationMethodDevices property + * Sets the authenticationMethodDevices property value. Exposes the hardware OATH method in the directory. * @param AuthenticationMethodDevice|null $value Value to set for the authenticationMethodDevices property. */ public function setAuthenticationMethodDevices(?AuthenticationMethodDevice $value): void { diff --git a/src/Generated/Models/EducationalActivityDetail.php b/src/Generated/Models/EducationalActivityDetail.php index ea05a73952b..d7c2a26231a 100644 --- a/src/Generated/Models/EducationalActivityDetail.php +++ b/src/Generated/Models/EducationalActivityDetail.php @@ -109,7 +109,7 @@ public function getDescription(): ?string { } /** - * Gets the displayName property value. Long-form name of the program that the user has provided. + * Gets the displayName property value. Long-form name of the program that the user provided. * @return string|null */ public function getDisplayName(): ?string { @@ -176,7 +176,7 @@ public function getFieldsOfStudy(): ?array { } /** - * Gets the grade property value. The final grade, class, GPA or score. + * Gets the grade property value. The final grade, class, GPA, or score. * @return string|null */ public function getGrade(): ?string { @@ -188,7 +188,7 @@ public function getGrade(): ?string { } /** - * Gets the notes property value. Additional notes the user has provided. + * Gets the notes property value. More notes the user provided. * @return string|null */ public function getNotes(): ?string { @@ -290,7 +290,7 @@ public function setDescription(?string $value): void { } /** - * Sets the displayName property value. Long-form name of the program that the user has provided. + * Sets the displayName property value. Long-form name of the program that the user provided. * @param string|null $value Value to set for the displayName property. */ public function setDisplayName(?string $value): void { @@ -306,7 +306,7 @@ public function setFieldsOfStudy(?array $value): void { } /** - * Sets the grade property value. The final grade, class, GPA or score. + * Sets the grade property value. The final grade, class, GPA, or score. * @param string|null $value Value to set for the grade property. */ public function setGrade(?string $value): void { @@ -314,7 +314,7 @@ public function setGrade(?string $value): void { } /** - * Sets the notes property value. Additional notes the user has provided. + * Sets the notes property value. More notes the user provided. * @param string|null $value Value to set for the notes property. */ public function setNotes(?string $value): void { diff --git a/src/Generated/Models/ExpirationPattern.php b/src/Generated/Models/ExpirationPattern.php index 7efbe518290..51d9118525f 100644 --- a/src/Generated/Models/ExpirationPattern.php +++ b/src/Generated/Models/ExpirationPattern.php @@ -58,7 +58,7 @@ public function getBackingStore(): BackingStore { } /** - * Gets the duration property value. The requestor's desired duration of access represented in ISO 8601 format for durations. For example, PT3H refers to three hours. If specified in a request, endDateTime should not be present and the type property should be set to afterDuration. + * Gets the duration property value. The requestor's desired duration of access represented in ISO 8601 format for durations. For example, PT3H refers to three hours. If specified in a request, endDateTime shouldn't be present and the type property should be set to afterDuration. * @return DateInterval|null */ public function getDuration(): ?DateInterval { @@ -70,7 +70,7 @@ public function getDuration(): ?DateInterval { } /** - * Gets the endDateTime property value. Timestamp of date and time information using ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 is 2014-01-01T00:00:00Z. + * Gets the endDateTime property value. Timestamp of date and time information using ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014, is 2014-01-01T00:00:00Z. * @return DateTime|null */ public function getEndDateTime(): ?DateTime { @@ -148,7 +148,7 @@ public function setBackingStore(BackingStore $value): void { } /** - * Sets the duration property value. The requestor's desired duration of access represented in ISO 8601 format for durations. For example, PT3H refers to three hours. If specified in a request, endDateTime should not be present and the type property should be set to afterDuration. + * Sets the duration property value. The requestor's desired duration of access represented in ISO 8601 format for durations. For example, PT3H refers to three hours. If specified in a request, endDateTime shouldn't be present and the type property should be set to afterDuration. * @param DateInterval|null $value Value to set for the duration property. */ public function setDuration(?DateInterval $value): void { @@ -156,7 +156,7 @@ public function setDuration(?DateInterval $value): void { } /** - * Sets the endDateTime property value. Timestamp of date and time information using ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 is 2014-01-01T00:00:00Z. + * Sets the endDateTime property value. Timestamp of date and time information using ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014, is 2014-01-01T00:00:00Z. * @param DateTime|null $value Value to set for the endDateTime property. */ public function setEndDateTime(?DateTime $value): void { diff --git a/src/Generated/Models/ExternalConnectors/Configuration.php b/src/Generated/Models/ExternalConnectors/Configuration.php index d626cefe411..30f2dba5a57 100644 --- a/src/Generated/Models/ExternalConnectors/Configuration.php +++ b/src/Generated/Models/ExternalConnectors/Configuration.php @@ -49,7 +49,7 @@ public function getAdditionalData(): ?array { } /** - * Gets the authorizedAppIds property value. A collection of application IDs for registered Microsoft Entra apps that are allowed to manage the externalConnection and to index content in the externalConnection. + * Gets the authorizedAppIds property value. A collection of application IDs for registered Microsoft Entra apps allowed to manage the externalConnection and index content in the externalConnection. * @return array|null */ public function getAuthorizedAppIds(): ?array { @@ -120,7 +120,7 @@ public function setAdditionalData(?array $value): void { } /** - * Sets the authorizedAppIds property value. A collection of application IDs for registered Microsoft Entra apps that are allowed to manage the externalConnection and to index content in the externalConnection. + * Sets the authorizedAppIds property value. A collection of application IDs for registered Microsoft Entra apps allowed to manage the externalConnection and index content in the externalConnection. * @param array|null $value Value to set for the authorizedAppIds property. */ public function setAuthorizedAppIds(?array $value): void { diff --git a/src/Generated/Models/ExternalConnectors/External.php b/src/Generated/Models/ExternalConnectors/External.php index 407061023bc..9dee10e0c49 100644 --- a/src/Generated/Models/ExternalConnectors/External.php +++ b/src/Generated/Models/ExternalConnectors/External.php @@ -51,7 +51,7 @@ public function getAdditionalData(): ?array { } /** - * Gets the authorizationSystems property value. Represents an onboarded AWS account, Azure subscription, or GCP project that Microsoft Entra Permissions Management will collect and analyze permissions and actions on. + * Gets the authorizationSystems property value. Represents an onboarded Amazon Web Services (AWS) account, Azure subscription, or Google Cloud Platform (GCP) project that Microsoft Entra Permissions Management collects and analyzes permissions and actions on. * @return array|null */ public function getAuthorizationSystems(): ?array { @@ -145,7 +145,7 @@ public function setAdditionalData(?array $value): void { } /** - * Sets the authorizationSystems property value. Represents an onboarded AWS account, Azure subscription, or GCP project that Microsoft Entra Permissions Management will collect and analyze permissions and actions on. + * Sets the authorizationSystems property value. Represents an onboarded Amazon Web Services (AWS) account, Azure subscription, or Google Cloud Platform (GCP) project that Microsoft Entra Permissions Management collects and analyzes permissions and actions on. * @param array|null $value Value to set for the authorizationSystems property. */ public function setAuthorizationSystems(?array $value): void { diff --git a/src/Generated/Models/HardwareOathAuthenticationMethod.php b/src/Generated/Models/HardwareOathAuthenticationMethod.php index da38b1d0e9e..1cfb6f0b1fc 100644 --- a/src/Generated/Models/HardwareOathAuthenticationMethod.php +++ b/src/Generated/Models/HardwareOathAuthenticationMethod.php @@ -26,7 +26,7 @@ public static function createFromDiscriminatorValue(ParseNode $parseNode): Hardw } /** - * Gets the device property value. The device property + * Gets the device property value. Exposes the hardware OATH method in the directory. * @return HardwareOathTokenAuthenticationMethodDevice|null */ public function getDevice(): ?HardwareOathTokenAuthenticationMethodDevice { @@ -58,7 +58,7 @@ public function serialize(SerializationWriter $writer): void { } /** - * Sets the device property value. The device property + * Sets the device property value. Exposes the hardware OATH method in the directory. * @param HardwareOathTokenAuthenticationMethodDevice|null $value Value to set for the device property. */ public function setDevice(?HardwareOathTokenAuthenticationMethodDevice $value): void { diff --git a/src/Generated/Models/HardwareOathTokenAuthenticationMethodDevice.php b/src/Generated/Models/HardwareOathTokenAuthenticationMethodDevice.php index b8ba246b015..4cbd94b03b1 100644 --- a/src/Generated/Models/HardwareOathTokenAuthenticationMethodDevice.php +++ b/src/Generated/Models/HardwareOathTokenAuthenticationMethodDevice.php @@ -26,7 +26,7 @@ public static function createFromDiscriminatorValue(ParseNode $parseNode): Hardw } /** - * Gets the assignedTo property value. The assignedTo property + * Gets the assignedTo property value. User the token is assigned to. Nullable. Supports $filter (eq). * @return Identity|null */ public function getAssignedTo(): ?Identity { @@ -38,7 +38,7 @@ public function getAssignedTo(): ?Identity { } /** - * Gets the assignTo property value. The assignTo property + * Gets the assignTo property value. Assign the hardware OATH token to a user. * @return User|null */ public function getAssignTo(): ?User { @@ -69,7 +69,7 @@ public function getFieldDeserializers(): array { } /** - * Gets the hashFunction property value. The hashFunction property + * Gets the hashFunction property value. Hash function of the hardrware token. The possible values are: hmacsha1 or hmacsha256. Default value is: hmacsha1. Supports $filter (eq). * @return HardwareOathTokenHashFunction|null */ public function getHashFunction(): ?HardwareOathTokenHashFunction { @@ -81,7 +81,7 @@ public function getHashFunction(): ?HardwareOathTokenHashFunction { } /** - * Gets the manufacturer property value. The manufacturer property + * Gets the manufacturer property value. Manufacturer name of the hardware token. Supports $filter (eq). * @return string|null */ public function getManufacturer(): ?string { @@ -93,7 +93,7 @@ public function getManufacturer(): ?string { } /** - * Gets the model property value. The model property + * Gets the model property value. Model name of the hardware token. Supports $filter (eq). * @return string|null */ public function getModel(): ?string { @@ -105,7 +105,7 @@ public function getModel(): ?string { } /** - * Gets the secretKey property value. The secretKey property + * Gets the secretKey property value. Secret key of the specific hardware token, provided by the vendor. * @return string|null */ public function getSecretKey(): ?string { @@ -117,7 +117,7 @@ public function getSecretKey(): ?string { } /** - * Gets the serialNumber property value. The serialNumber property + * Gets the serialNumber property value. Serial number of the specific hardware token, often found on the back of the device. Supports $select and $filter (eq). * @return string|null */ public function getSerialNumber(): ?string { @@ -129,7 +129,7 @@ public function getSerialNumber(): ?string { } /** - * Gets the status property value. The status property + * Gets the status property value. Status of the hardware OATH token.The possible values are: available, assigned, activated, failedActivation. Supports $filter(eq). * @return HardwareOathTokenStatus|null */ public function getStatus(): ?HardwareOathTokenStatus { @@ -141,7 +141,7 @@ public function getStatus(): ?HardwareOathTokenStatus { } /** - * Gets the timeIntervalInSeconds property value. The timeIntervalInSeconds property + * Gets the timeIntervalInSeconds property value. Refresh interval of the 6-digit verification code, in seconds. The possible values are: 30 or 60. Supports $filter (eq). * @return int|null */ public function getTimeIntervalInSeconds(): ?int { @@ -170,7 +170,7 @@ public function serialize(SerializationWriter $writer): void { } /** - * Sets the assignedTo property value. The assignedTo property + * Sets the assignedTo property value. User the token is assigned to. Nullable. Supports $filter (eq). * @param Identity|null $value Value to set for the assignedTo property. */ public function setAssignedTo(?Identity $value): void { @@ -178,7 +178,7 @@ public function setAssignedTo(?Identity $value): void { } /** - * Sets the assignTo property value. The assignTo property + * Sets the assignTo property value. Assign the hardware OATH token to a user. * @param User|null $value Value to set for the assignTo property. */ public function setAssignTo(?User $value): void { @@ -186,7 +186,7 @@ public function setAssignTo(?User $value): void { } /** - * Sets the hashFunction property value. The hashFunction property + * Sets the hashFunction property value. Hash function of the hardrware token. The possible values are: hmacsha1 or hmacsha256. Default value is: hmacsha1. Supports $filter (eq). * @param HardwareOathTokenHashFunction|null $value Value to set for the hashFunction property. */ public function setHashFunction(?HardwareOathTokenHashFunction $value): void { @@ -194,7 +194,7 @@ public function setHashFunction(?HardwareOathTokenHashFunction $value): void { } /** - * Sets the manufacturer property value. The manufacturer property + * Sets the manufacturer property value. Manufacturer name of the hardware token. Supports $filter (eq). * @param string|null $value Value to set for the manufacturer property. */ public function setManufacturer(?string $value): void { @@ -202,7 +202,7 @@ public function setManufacturer(?string $value): void { } /** - * Sets the model property value. The model property + * Sets the model property value. Model name of the hardware token. Supports $filter (eq). * @param string|null $value Value to set for the model property. */ public function setModel(?string $value): void { @@ -210,7 +210,7 @@ public function setModel(?string $value): void { } /** - * Sets the secretKey property value. The secretKey property + * Sets the secretKey property value. Secret key of the specific hardware token, provided by the vendor. * @param string|null $value Value to set for the secretKey property. */ public function setSecretKey(?string $value): void { @@ -218,7 +218,7 @@ public function setSecretKey(?string $value): void { } /** - * Sets the serialNumber property value. The serialNumber property + * Sets the serialNumber property value. Serial number of the specific hardware token, often found on the back of the device. Supports $select and $filter (eq). * @param string|null $value Value to set for the serialNumber property. */ public function setSerialNumber(?string $value): void { @@ -226,7 +226,7 @@ public function setSerialNumber(?string $value): void { } /** - * Sets the status property value. The status property + * Sets the status property value. Status of the hardware OATH token.The possible values are: available, assigned, activated, failedActivation. Supports $filter(eq). * @param HardwareOathTokenStatus|null $value Value to set for the status property. */ public function setStatus(?HardwareOathTokenStatus $value): void { @@ -234,7 +234,7 @@ public function setStatus(?HardwareOathTokenStatus $value): void { } /** - * Sets the timeIntervalInSeconds property value. The timeIntervalInSeconds property + * Sets the timeIntervalInSeconds property value. Refresh interval of the 6-digit verification code, in seconds. The possible values are: 30 or 60. Supports $filter (eq). * @param int|null $value Value to set for the timeIntervalInSeconds property. */ public function setTimeIntervalInSeconds(?int $value): void { diff --git a/src/Generated/Models/Identity.php b/src/Generated/Models/Identity.php index ad680fa0677..38a6d49dde9 100644 --- a/src/Generated/Models/Identity.php +++ b/src/Generated/Models/Identity.php @@ -89,7 +89,7 @@ public function getBackingStore(): BackingStore { } /** - * Gets the displayName property value. The display name of the identity. For drive items, the display name might not always be available or up to date. For example, if a user changes their display name the API might show the new value in a future response, but the items associated with the user don't show up as changed when using delta. + * Gets the displayName property value. The display name of the identity. This property is read-only. * @return string|null */ public function getDisplayName(): ?string { @@ -114,7 +114,7 @@ public function getFieldDeserializers(): array { } /** - * Gets the id property value. Unique identifier for the identity or actor. For example, in the access reviews decisions API, this property might record the id of the principal, that is, the group, user, or application that's subject to review. + * Gets the id property value. The identifier of the identity. This property is read-only. * @return string|null */ public function getId(): ?string { @@ -165,7 +165,7 @@ public function setBackingStore(BackingStore $value): void { } /** - * Sets the displayName property value. The display name of the identity. For drive items, the display name might not always be available or up to date. For example, if a user changes their display name the API might show the new value in a future response, but the items associated with the user don't show up as changed when using delta. + * Sets the displayName property value. The display name of the identity. This property is read-only. * @param string|null $value Value to set for the displayName property. */ public function setDisplayName(?string $value): void { @@ -173,7 +173,7 @@ public function setDisplayName(?string $value): void { } /** - * Sets the id property value. Unique identifier for the identity or actor. For example, in the access reviews decisions API, this property might record the id of the principal, that is, the group, user, or application that's subject to review. + * Sets the id property value. The identifier of the identity. This property is read-only. * @param string|null $value Value to set for the id property. */ public function setId(?string $value): void { diff --git a/src/Generated/Models/IdentitySet.php b/src/Generated/Models/IdentitySet.php index d598ea70632..7a025127eda 100644 --- a/src/Generated/Models/IdentitySet.php +++ b/src/Generated/Models/IdentitySet.php @@ -60,7 +60,7 @@ public function getAdditionalData(): ?array { } /** - * Gets the application property value. The Identity of the Application. This property is read-only. + * Gets the application property value. Optional. The application associated with this action. * @return Identity|null */ public function getApplication(): ?Identity { @@ -80,7 +80,7 @@ public function getBackingStore(): BackingStore { } /** - * Gets the device property value. The Identity of the Device. This property is read-only. + * Gets the device property value. Optional. The device associated with this action. * @return Identity|null */ public function getDevice(): ?Identity { @@ -118,7 +118,7 @@ public function getOdataType(): ?string { } /** - * Gets the user property value. The Identity of the User. This property is read-only. + * Gets the user property value. Optional. The user associated with this action. * @return Identity|null */ public function getUser(): ?Identity { @@ -150,7 +150,7 @@ public function setAdditionalData(?array $value): void { } /** - * Sets the application property value. The Identity of the Application. This property is read-only. + * Sets the application property value. Optional. The application associated with this action. * @param Identity|null $value Value to set for the application property. */ public function setApplication(?Identity $value): void { @@ -166,7 +166,7 @@ public function setBackingStore(BackingStore $value): void { } /** - * Sets the device property value. The Identity of the Device. This property is read-only. + * Sets the device property value. Optional. The device associated with this action. * @param Identity|null $value Value to set for the device property. */ public function setDevice(?Identity $value): void { @@ -182,7 +182,7 @@ public function setOdataType(?string $value): void { } /** - * Sets the user property value. The Identity of the User. This property is read-only. + * Sets the user property value. Optional. The user associated with this action. * @param Identity|null $value Value to set for the user property. */ public function setUser(?Identity $value): void { diff --git a/src/Generated/Models/Initiator.php b/src/Generated/Models/Initiator.php index 5691c9c9b56..7a27a438325 100644 --- a/src/Generated/Models/Initiator.php +++ b/src/Generated/Models/Initiator.php @@ -37,7 +37,7 @@ public function getFieldDeserializers(): array { } /** - * Gets the initiatorType property value. Type of initiator. Possible values are: user, application, system, unknownFutureValue. + * Gets the initiatorType property value. The type of the initiator. Possible values are: user, application, system, unknownFutureValue. * @return InitiatorType|null */ public function getInitiatorType(): ?InitiatorType { @@ -58,7 +58,7 @@ public function serialize(SerializationWriter $writer): void { } /** - * Sets the initiatorType property value. Type of initiator. Possible values are: user, application, system, unknownFutureValue. + * Sets the initiatorType property value. The type of the initiator. Possible values are: user, application, system, unknownFutureValue. * @param InitiatorType|null $value Value to set for the initiatorType property. */ public function setInitiatorType(?InitiatorType $value): void { diff --git a/src/Generated/Models/ItemAttachment.php b/src/Generated/Models/ItemAttachment.php index 3acf434d865..b9ddb123aee 100644 --- a/src/Generated/Models/ItemAttachment.php +++ b/src/Generated/Models/ItemAttachment.php @@ -37,7 +37,7 @@ public function getFieldDeserializers(): array { } /** - * Gets the item property value. The attached contact, message or event. Navigation property. + * Gets the item property value. The attached contact, message, or event. Navigation property. * @return OutlookItem|null */ public function getItem(): ?OutlookItem { @@ -58,7 +58,7 @@ public function serialize(SerializationWriter $writer): void { } /** - * Sets the item property value. The attached contact, message or event. Navigation property. + * Sets the item property value. The attached contact, message, or event. Navigation property. * @param OutlookItem|null $value Value to set for the item property. */ public function setItem(?OutlookItem $value): void { diff --git a/src/Generated/Models/KeyValuePair.php b/src/Generated/Models/KeyValuePair.php index 4a95566fc66..1fe52d11504 100644 --- a/src/Generated/Models/KeyValuePair.php +++ b/src/Generated/Models/KeyValuePair.php @@ -69,7 +69,7 @@ public function getFieldDeserializers(): array { } /** - * Gets the name property value. Name for this key-value pair. For more information about possible names for each resource type that uses this configuration, see keyValuePair names and values. + * Gets the name property value. Name for this key-value pair * @return string|null */ public function getName(): ?string { @@ -93,7 +93,7 @@ public function getOdataType(): ?string { } /** - * Gets the value property value. Value for this key-value pair. For more information about possible values for each resource type that uses this configuration, see keyValuePair names and values. + * Gets the value property value. Value for this key-value pair * @return string|null */ public function getValue(): ?string { @@ -132,7 +132,7 @@ public function setBackingStore(BackingStore $value): void { } /** - * Sets the name property value. Name for this key-value pair. For more information about possible names for each resource type that uses this configuration, see keyValuePair names and values. + * Sets the name property value. Name for this key-value pair * @param string|null $value Value to set for the name property. */ public function setName(?string $value): void { @@ -148,7 +148,7 @@ public function setOdataType(?string $value): void { } /** - * Sets the value property value. Value for this key-value pair. For more information about possible values for each resource type that uses this configuration, see keyValuePair names and values. + * Sets the value property value. Value for this key-value pair * @param string|null $value Value to set for the value property. */ public function setValue(?string $value): void { diff --git a/src/Generated/Models/MacOsLobAppAssignmentSettings.php b/src/Generated/Models/MacOsLobAppAssignmentSettings.php index 49f681a8027..0ef926d94fb 100644 --- a/src/Generated/Models/MacOsLobAppAssignmentSettings.php +++ b/src/Generated/Models/MacOsLobAppAssignmentSettings.php @@ -40,7 +40,7 @@ public function getFieldDeserializers(): array { } /** - * Gets the uninstallOnDeviceRemoval property value. Whether or not to uninstall the app when device is removed from Intune. + * Gets the uninstallOnDeviceRemoval property value. When TRUE, indicates that the app should be uninstalled when the device is removed from Intune. When FALSE, indicates that the app will not be uninstalled when the device is removed from Intune. * @return bool|null */ public function getUninstallOnDeviceRemoval(): ?bool { @@ -61,7 +61,7 @@ public function serialize(SerializationWriter $writer): void { } /** - * Sets the uninstallOnDeviceRemoval property value. Whether or not to uninstall the app when device is removed from Intune. + * Sets the uninstallOnDeviceRemoval property value. When TRUE, indicates that the app should be uninstalled when the device is removed from Intune. When FALSE, indicates that the app will not be uninstalled when the device is removed from Intune. * @param bool|null $value Value to set for the uninstallOnDeviceRemoval property. */ public function setUninstallOnDeviceRemoval(?bool $value): void { diff --git a/src/Generated/Models/MailTips.php b/src/Generated/Models/MailTips.php index b5fa3552e72..57fd68fa949 100644 --- a/src/Generated/Models/MailTips.php +++ b/src/Generated/Models/MailTips.php @@ -49,7 +49,7 @@ public function getAdditionalData(): ?array { } /** - * Gets the automaticReplies property value. Mail tips for automatic reply if it has been set up by the recipient. + * Gets the automaticReplies property value. Mailtips for an automatic reply if set up by the recipient. * @return AutomaticRepliesMailTips|null */ public function getAutomaticReplies(): ?AutomaticRepliesMailTips { @@ -81,7 +81,7 @@ public function getCustomMailTip(): ?string { } /** - * Gets the deliveryRestricted property value. Whether the recipient's mailbox is restricted, for example, accepting messages from only a predefined list of senders, rejecting messages from a predefined list of senders, or accepting messages from only authenticated senders. + * Gets the deliveryRestricted property value. Whether the recipient's mailbox is restricted. For example, accepting messages from only a predefined list of senders, rejecting messages from a predefined list of senders, or accepting messages from only authenticated senders. * @return bool|null */ public function getDeliveryRestricted(): ?bool { @@ -152,7 +152,7 @@ public function getFieldDeserializers(): array { } /** - * Gets the isModerated property value. Whether sending messages to the recipient requires approval. For example, if the recipient is a large distribution list and a moderator has been set up to approve messages sent to that distribution list, or if sending messages to a recipient requires approval of the recipient's manager. + * Gets the isModerated property value. Whether sending messages to the recipient requires approval. For example, if the recipient is a large distribution list and a moderator is set up to approve messages sent to that distribution list, or if sending messages to a recipient requires approval of the recipient's manager. * @return bool|null */ public function getIsModerated(): ?bool { @@ -176,7 +176,7 @@ public function getMailboxFull(): ?bool { } /** - * Gets the maxMessageSize property value. The maximum message size that has been configured for the recipient's organization or mailbox. + * Gets the maxMessageSize property value. The maximum message size configured for the recipient's organization or mailbox. * @return int|null */ public function getMaxMessageSize(): ?int { @@ -200,7 +200,7 @@ public function getOdataType(): ?string { } /** - * Gets the recipientScope property value. The scope of the recipient. Possible values are: none, internal, external, externalPartner, externalNonParther. For example, an administrator can set another organization to be its 'partner'. The scope is useful if an administrator wants certain mailtips to be accessible to certain scopes. It's also useful to senders to inform them that their message may leave the organization, helping them make the correct decisions about wording, tone and content. + * Gets the recipientScope property value. The scope of the recipient. Possible values are: none, internal, external, externalPartner, externalNonParther. For example, an administrator can set another organization to be its 'partner'. The scope is useful if an administrator wants certain mailtips to be accessible to certain scopes. It's also useful to senders to inform them that their message may leave the organization, helping them make the correct decisions about wording, tone, and content. * @return RecipientScopeType|null */ public function getRecipientScope(): ?RecipientScopeType { @@ -267,7 +267,7 @@ public function setAdditionalData(?array $value): void { } /** - * Sets the automaticReplies property value. Mail tips for automatic reply if it has been set up by the recipient. + * Sets the automaticReplies property value. Mailtips for an automatic reply if set up by the recipient. * @param AutomaticRepliesMailTips|null $value Value to set for the automaticReplies property. */ public function setAutomaticReplies(?AutomaticRepliesMailTips $value): void { @@ -291,7 +291,7 @@ public function setCustomMailTip(?string $value): void { } /** - * Sets the deliveryRestricted property value. Whether the recipient's mailbox is restricted, for example, accepting messages from only a predefined list of senders, rejecting messages from a predefined list of senders, or accepting messages from only authenticated senders. + * Sets the deliveryRestricted property value. Whether the recipient's mailbox is restricted. For example, accepting messages from only a predefined list of senders, rejecting messages from a predefined list of senders, or accepting messages from only authenticated senders. * @param bool|null $value Value to set for the deliveryRestricted property. */ public function setDeliveryRestricted(?bool $value): void { @@ -323,7 +323,7 @@ public function setExternalMemberCount(?int $value): void { } /** - * Sets the isModerated property value. Whether sending messages to the recipient requires approval. For example, if the recipient is a large distribution list and a moderator has been set up to approve messages sent to that distribution list, or if sending messages to a recipient requires approval of the recipient's manager. + * Sets the isModerated property value. Whether sending messages to the recipient requires approval. For example, if the recipient is a large distribution list and a moderator is set up to approve messages sent to that distribution list, or if sending messages to a recipient requires approval of the recipient's manager. * @param bool|null $value Value to set for the isModerated property. */ public function setIsModerated(?bool $value): void { @@ -339,7 +339,7 @@ public function setMailboxFull(?bool $value): void { } /** - * Sets the maxMessageSize property value. The maximum message size that has been configured for the recipient's organization or mailbox. + * Sets the maxMessageSize property value. The maximum message size configured for the recipient's organization or mailbox. * @param int|null $value Value to set for the maxMessageSize property. */ public function setMaxMessageSize(?int $value): void { @@ -355,7 +355,7 @@ public function setOdataType(?string $value): void { } /** - * Sets the recipientScope property value. The scope of the recipient. Possible values are: none, internal, external, externalPartner, externalNonParther. For example, an administrator can set another organization to be its 'partner'. The scope is useful if an administrator wants certain mailtips to be accessible to certain scopes. It's also useful to senders to inform them that their message may leave the organization, helping them make the correct decisions about wording, tone and content. + * Sets the recipientScope property value. The scope of the recipient. Possible values are: none, internal, external, externalPartner, externalNonParther. For example, an administrator can set another organization to be its 'partner'. The scope is useful if an administrator wants certain mailtips to be accessible to certain scopes. It's also useful to senders to inform them that their message may leave the organization, helping them make the correct decisions about wording, tone, and content. * @param RecipientScopeType|null $value Value to set for the recipientScope property. */ public function setRecipientScope(?RecipientScopeType $value): void { diff --git a/src/Generated/Models/MailboxRestoreArtifact.php b/src/Generated/Models/MailboxRestoreArtifact.php index d50e2a4fb1b..74819441a10 100644 --- a/src/Generated/Models/MailboxRestoreArtifact.php +++ b/src/Generated/Models/MailboxRestoreArtifact.php @@ -45,7 +45,7 @@ public function getFieldDeserializers(): array { } /** - * Gets the restoredFolderId property value. The new restored folder identifier for the user. + * Gets the restoredFolderId property value. The newly restored folder identifier for the user. * @return string|null */ public function getRestoredFolderId(): ?string { @@ -69,7 +69,7 @@ public function getRestoredFolderName(): ?string { } /** - * Gets the restoredItemCount property value. The restoredItemCount property + * Gets the restoredItemCount property value. The number of items that are being restored in the folder. * @return int|null */ public function getRestoredItemCount(): ?int { @@ -91,7 +91,7 @@ public function serialize(SerializationWriter $writer): void { } /** - * Sets the restoredFolderId property value. The new restored folder identifier for the user. + * Sets the restoredFolderId property value. The newly restored folder identifier for the user. * @param string|null $value Value to set for the restoredFolderId property. */ public function setRestoredFolderId(?string $value): void { @@ -107,7 +107,7 @@ public function setRestoredFolderName(?string $value): void { } /** - * Sets the restoredItemCount property value. The restoredItemCount property + * Sets the restoredItemCount property value. The number of items that are being restored in the folder. * @param int|null $value Value to set for the restoredItemCount property. */ public function setRestoredItemCount(?int $value): void { diff --git a/src/Generated/Models/Networkaccess/Connectivity.php b/src/Generated/Models/Networkaccess/Connectivity.php index 4ea44c0a58a..07fc2362bb9 100644 --- a/src/Generated/Models/Networkaccess/Connectivity.php +++ b/src/Generated/Models/Networkaccess/Connectivity.php @@ -27,7 +27,7 @@ public static function createFromDiscriminatorValue(ParseNode $parseNode): Conne } /** - * Gets the branches property value. Branches represent locations for connectivity. DEPRECATED AND TO BE RETIRED SOON. Use the remoteNetwork relationship and its associated APIs instead. + * Gets the branches property value. The locations for connectivity. DEPRECATED AND TO BE RETIRED SOON. Use the remoteNetwork relationship and its associated APIs instead. * @return array|null */ public function getBranches(): ?array { @@ -54,7 +54,7 @@ public function getFieldDeserializers(): array { } /** - * Gets the remoteNetworks property value. Represent locations, such as branches, that are connected to Global Secure Access services through an IPsec tunnel. + * Gets the remoteNetworks property value. The locations, such as branches, that are connected to Global Secure Access services through an IPsec tunnel. * @return array|null */ public function getRemoteNetworks(): ?array { @@ -93,7 +93,7 @@ public function serialize(SerializationWriter $writer): void { } /** - * Sets the branches property value. Branches represent locations for connectivity. DEPRECATED AND TO BE RETIRED SOON. Use the remoteNetwork relationship and its associated APIs instead. + * Sets the branches property value. The locations for connectivity. DEPRECATED AND TO BE RETIRED SOON. Use the remoteNetwork relationship and its associated APIs instead. * @param array|null $value Value to set for the branches property. */ public function setBranches(?array $value): void { @@ -101,7 +101,7 @@ public function setBranches(?array $value): void { } /** - * Sets the remoteNetworks property value. Represent locations, such as branches, that are connected to Global Secure Access services through an IPsec tunnel. + * Sets the remoteNetworks property value. The locations, such as branches, that are connected to Global Secure Access services through an IPsec tunnel. * @param array|null $value Value to set for the remoteNetworks property. */ public function setRemoteNetworks(?array $value): void { diff --git a/src/Generated/Models/Networkaccess/Profile.php b/src/Generated/Models/Networkaccess/Profile.php index 27675ebb4a6..88b90b42a5a 100644 --- a/src/Generated/Models/Networkaccess/Profile.php +++ b/src/Generated/Models/Networkaccess/Profile.php @@ -64,7 +64,7 @@ public function getFieldDeserializers(): array { } /** - * Gets the lastModifiedDateTime property value. Profile last modified time. + * Gets the lastModifiedDateTime property value. The date and time when the profile was last modified. * @return DateTime|null */ public function getLastModifiedDateTime(): ?DateTime { @@ -76,7 +76,7 @@ public function getLastModifiedDateTime(): ?DateTime { } /** - * Gets the name property value. Profile name. + * Gets the name property value. The name of the profile. * @return string|null */ public function getName(): ?string { @@ -88,7 +88,7 @@ public function getName(): ?string { } /** - * Gets the policies property value. Traffic forwarding policies associated with this profile. + * Gets the policies property value. The traffic forwarding policies associated with this profile. * @return array|null */ public function getPolicies(): ?array { @@ -148,7 +148,7 @@ public function setDescription(?string $value): void { } /** - * Sets the lastModifiedDateTime property value. Profile last modified time. + * Sets the lastModifiedDateTime property value. The date and time when the profile was last modified. * @param DateTime|null $value Value to set for the lastModifiedDateTime property. */ public function setLastModifiedDateTime(?DateTime $value): void { @@ -156,7 +156,7 @@ public function setLastModifiedDateTime(?DateTime $value): void { } /** - * Sets the name property value. Profile name. + * Sets the name property value. The name of the profile. * @param string|null $value Value to set for the name property. */ public function setName(?string $value): void { @@ -164,7 +164,7 @@ public function setName(?string $value): void { } /** - * Sets the policies property value. Traffic forwarding policies associated with this profile. + * Sets the policies property value. The traffic forwarding policies associated with this profile. * @param array|null $value Value to set for the policies property. */ public function setPolicies(?array $value): void { diff --git a/src/Generated/Models/NewsLinkPage.php b/src/Generated/Models/NewsLinkPage.php index 1c8d41a3eb6..4cb7c247a9d 100644 --- a/src/Generated/Models/NewsLinkPage.php +++ b/src/Generated/Models/NewsLinkPage.php @@ -25,7 +25,7 @@ public static function createFromDiscriminatorValue(ParseNode $parseNode): NewsL } /** - * Gets the bannerImageWebUrl property value. The bannerImageWebUrl property + * Gets the bannerImageWebUrl property value. A link to the banner image for the newsLinkPage. * @return string|null */ public function getBannerImageWebUrl(): ?string { @@ -50,7 +50,7 @@ public function getFieldDeserializers(): array { } /** - * Gets the newsSharepointIds property value. The newsSharepointIds property + * Gets the newsSharepointIds property value. The SharePoint IDs of the referenced news article if it's recognized as a SharePoint resource. Read-only. * @return SharepointIds|null */ public function getNewsSharepointIds(): ?SharepointIds { @@ -62,7 +62,7 @@ public function getNewsSharepointIds(): ?SharepointIds { } /** - * Gets the newsWebUrl property value. The newsWebUrl property + * Gets the newsWebUrl property value. The URL of the news article referenced by the newsLinkPage. It can be an external link. * @return string|null */ public function getNewsWebUrl(): ?string { @@ -85,7 +85,7 @@ public function serialize(SerializationWriter $writer): void { } /** - * Sets the bannerImageWebUrl property value. The bannerImageWebUrl property + * Sets the bannerImageWebUrl property value. A link to the banner image for the newsLinkPage. * @param string|null $value Value to set for the bannerImageWebUrl property. */ public function setBannerImageWebUrl(?string $value): void { @@ -93,7 +93,7 @@ public function setBannerImageWebUrl(?string $value): void { } /** - * Sets the newsSharepointIds property value. The newsSharepointIds property + * Sets the newsSharepointIds property value. The SharePoint IDs of the referenced news article if it's recognized as a SharePoint resource. Read-only. * @param SharepointIds|null $value Value to set for the newsSharepointIds property. */ public function setNewsSharepointIds(?SharepointIds $value): void { @@ -101,7 +101,7 @@ public function setNewsSharepointIds(?SharepointIds $value): void { } /** - * Sets the newsWebUrl property value. The newsWebUrl property + * Sets the newsWebUrl property value. The URL of the news article referenced by the newsLinkPage. It can be an external link. * @param string|null $value Value to set for the newsWebUrl property. */ public function setNewsWebUrl(?string $value): void { diff --git a/src/Generated/Models/OnAttributeCollectionExternalUsersSelfServiceSignUp.php b/src/Generated/Models/OnAttributeCollectionExternalUsersSelfServiceSignUp.php index f6cee19ffd9..0198bea3b66 100644 --- a/src/Generated/Models/OnAttributeCollectionExternalUsersSelfServiceSignUp.php +++ b/src/Generated/Models/OnAttributeCollectionExternalUsersSelfServiceSignUp.php @@ -27,7 +27,7 @@ public static function createFromDiscriminatorValue(ParseNode $parseNode): OnAtt } /** - * Gets the attributeCollectionPage property value. Required. The configuration for how attributes are displayed in the sign up experience defined by a user flow, like the externalUsersSelfServiceSignupEventsFlow, specifically on the attribute collection page. + * Gets the attributeCollectionPage property value. Required. The configuration for how attributes are displayed in the sign-up experience defined by a user flow, like the externalUsersSelfServiceSignupEventsFlow, specifically on the attribute collection page. * @return AuthenticationAttributeCollectionPage|null */ public function getAttributeCollectionPage(): ?AuthenticationAttributeCollectionPage { @@ -75,7 +75,7 @@ public function serialize(SerializationWriter $writer): void { } /** - * Sets the attributeCollectionPage property value. Required. The configuration for how attributes are displayed in the sign up experience defined by a user flow, like the externalUsersSelfServiceSignupEventsFlow, specifically on the attribute collection page. + * Sets the attributeCollectionPage property value. Required. The configuration for how attributes are displayed in the sign-up experience defined by a user flow, like the externalUsersSelfServiceSignupEventsFlow, specifically on the attribute collection page. * @param AuthenticationAttributeCollectionPage|null $value Value to set for the attributeCollectionPage property. */ public function setAttributeCollectionPage(?AuthenticationAttributeCollectionPage $value): void { diff --git a/src/Generated/Models/OnInteractiveAuthFlowStartListener.php b/src/Generated/Models/OnInteractiveAuthFlowStartListener.php index ad0c59f2d87..e7698da9924 100644 --- a/src/Generated/Models/OnInteractiveAuthFlowStartListener.php +++ b/src/Generated/Models/OnInteractiveAuthFlowStartListener.php @@ -37,7 +37,7 @@ public function getFieldDeserializers(): array { } /** - * Gets the handler property value. Required. Configuration for what to invoke if the event resolves to this listener. This lets us define potential handler configurations per-event. + * Gets the handler property value. Required. Configuration for what to invoke if the event resolves to this listener. You can use this handler to define potential handler configurations for specific events. * @return OnInteractiveAuthFlowStartHandler|null */ public function getHandler(): ?OnInteractiveAuthFlowStartHandler { @@ -58,7 +58,7 @@ public function serialize(SerializationWriter $writer): void { } /** - * Sets the handler property value. Required. Configuration for what to invoke if the event resolves to this listener. This lets us define potential handler configurations per-event. + * Sets the handler property value. Required. Configuration for what to invoke if the event resolves to this listener. You can use this handler to define potential handler configurations for specific events. * @param OnInteractiveAuthFlowStartHandler|null $value Value to set for the handler property. */ public function setHandler(?OnInteractiveAuthFlowStartHandler $value): void { diff --git a/src/Generated/Models/OneDriveForBusinessProtectionPolicy.php b/src/Generated/Models/OneDriveForBusinessProtectionPolicy.php index f05977c567a..8abd835c9ec 100644 --- a/src/Generated/Models/OneDriveForBusinessProtectionPolicy.php +++ b/src/Generated/Models/OneDriveForBusinessProtectionPolicy.php @@ -27,7 +27,7 @@ public static function createFromDiscriminatorValue(ParseNode $parseNode): OneDr } /** - * Gets the driveInclusionRules property value. Contains the details of the Onedrive for Business protection rule. + * Gets the driveInclusionRules property value. Contains the details of the OneDrive for Work or School protection rule. * @return array|null */ public function getDriveInclusionRules(): ?array { @@ -41,7 +41,7 @@ public function getDriveInclusionRules(): ?array { } /** - * Gets the driveProtectionUnits property value. Contains the protection units associated with a OneDrive for Business protection policy. + * Gets the driveProtectionUnits property value. Contains the protection units associated with a OneDrive for Work or School protection policy. * @return array|null */ public function getDriveProtectionUnits(): ?array { @@ -93,7 +93,7 @@ public function serialize(SerializationWriter $writer): void { } /** - * Sets the driveInclusionRules property value. Contains the details of the Onedrive for Business protection rule. + * Sets the driveInclusionRules property value. Contains the details of the OneDrive for Work or School protection rule. * @param array|null $value Value to set for the driveInclusionRules property. */ public function setDriveInclusionRules(?array $value): void { @@ -101,7 +101,7 @@ public function setDriveInclusionRules(?array $value): void { } /** - * Sets the driveProtectionUnits property value. Contains the protection units associated with a OneDrive for Business protection policy. + * Sets the driveProtectionUnits property value. Contains the protection units associated with a OneDrive for Work or School protection policy. * @param array|null $value Value to set for the driveProtectionUnits property. */ public function setDriveProtectionUnits(?array $value): void { diff --git a/src/Generated/Models/OneDriveForBusinessRestoreSession.php b/src/Generated/Models/OneDriveForBusinessRestoreSession.php index 881ba25308c..82a3fbec303 100644 --- a/src/Generated/Models/OneDriveForBusinessRestoreSession.php +++ b/src/Generated/Models/OneDriveForBusinessRestoreSession.php @@ -27,7 +27,7 @@ public static function createFromDiscriminatorValue(ParseNode $parseNode): OneDr } /** - * Gets the driveRestoreArtifacts property value. A collection of restore points and destination details that can be used to restore a OneDrive for Business drive. + * Gets the driveRestoreArtifacts property value. A collection of restore points and destination details that can be used to restore a OneDrive for Work or School drive. * @return array|null */ public function getDriveRestoreArtifacts(): ?array { @@ -77,7 +77,7 @@ public function serialize(SerializationWriter $writer): void { } /** - * Sets the driveRestoreArtifacts property value. A collection of restore points and destination details that can be used to restore a OneDrive for Business drive. + * Sets the driveRestoreArtifacts property value. A collection of restore points and destination details that can be used to restore a OneDrive for Work or School drive. * @param array|null $value Value to set for the driveRestoreArtifacts property. */ public function setDriveRestoreArtifacts(?array $value): void { diff --git a/src/Generated/Models/Onenote.php b/src/Generated/Models/Onenote.php index 3e026bef03c..482f5e002c1 100644 --- a/src/Generated/Models/Onenote.php +++ b/src/Generated/Models/Onenote.php @@ -42,7 +42,7 @@ public function getFieldDeserializers(): array { } /** - * Gets the notebooks property value. The collection of OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * Gets the notebooks property value. The collection of OneNote notebooks that the user or group owns. Read-only. Nullable. * @return array|null */ public function getNotebooks(): ?array { @@ -70,7 +70,7 @@ public function getOperations(): ?array { } /** - * Gets the pages property value. The pages in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * Gets the pages property value. The pages in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @return array|null */ public function getPages(): ?array { @@ -98,7 +98,7 @@ public function getResources(): ?array { } /** - * Gets the sectionGroups property value. The section groups in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * Gets the sectionGroups property value. The section groups in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @return array|null */ public function getSectionGroups(): ?array { @@ -112,7 +112,7 @@ public function getSectionGroups(): ?array { } /** - * Gets the sections property value. The sections in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * Gets the sections property value. The sections in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @return array|null */ public function getSections(): ?array { @@ -140,7 +140,7 @@ public function serialize(SerializationWriter $writer): void { } /** - * Sets the notebooks property value. The collection of OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * Sets the notebooks property value. The collection of OneNote notebooks that the user or group owns. Read-only. Nullable. * @param array|null $value Value to set for the notebooks property. */ public function setNotebooks(?array $value): void { @@ -156,7 +156,7 @@ public function setOperations(?array $value): void { } /** - * Sets the pages property value. The pages in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * Sets the pages property value. The pages in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @param array|null $value Value to set for the pages property. */ public function setPages(?array $value): void { @@ -172,7 +172,7 @@ public function setResources(?array $value): void { } /** - * Sets the sectionGroups property value. The section groups in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * Sets the sectionGroups property value. The section groups in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @param array|null $value Value to set for the sectionGroups property. */ public function setSectionGroups(?array $value): void { @@ -180,7 +180,7 @@ public function setSectionGroups(?array $value): void { } /** - * Sets the sections property value. The sections in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * Sets the sections property value. The sections in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @param array|null $value Value to set for the sections property. */ public function setSections(?array $value): void { diff --git a/src/Generated/Models/RestoreSessionArtifactCount.php b/src/Generated/Models/RestoreSessionArtifactCount.php index eda5511e69b..d01aade9e1c 100644 --- a/src/Generated/Models/RestoreSessionArtifactCount.php +++ b/src/Generated/Models/RestoreSessionArtifactCount.php @@ -56,7 +56,7 @@ public function getBackingStore(): BackingStore { } /** - * Gets the completed property value. The completed property + * Gets the completed property value. The number of artifacts whose restoration completed. * @return int|null */ public function getCompleted(): ?int { @@ -68,7 +68,7 @@ public function getCompleted(): ?int { } /** - * Gets the failed property value. The failed property + * Gets the failed property value. The number of artifacts whose restoration failed. * @return int|null */ public function getFailed(): ?int { @@ -95,7 +95,7 @@ public function getFieldDeserializers(): array { } /** - * Gets the inProgress property value. The inProgress property + * Gets the inProgress property value. The number of artifacts whose restoration is in progress. * @return int|null */ public function getInProgress(): ?int { @@ -119,7 +119,7 @@ public function getOdataType(): ?string { } /** - * Gets the total property value. The total property + * Gets the total property value. The number of artifacts present in the restore session. * @return int|null */ public function getTotal(): ?int { @@ -160,7 +160,7 @@ public function setBackingStore(BackingStore $value): void { } /** - * Sets the completed property value. The completed property + * Sets the completed property value. The number of artifacts whose restoration completed. * @param int|null $value Value to set for the completed property. */ public function setCompleted(?int $value): void { @@ -168,7 +168,7 @@ public function setCompleted(?int $value): void { } /** - * Sets the failed property value. The failed property + * Sets the failed property value. The number of artifacts whose restoration failed. * @param int|null $value Value to set for the failed property. */ public function setFailed(?int $value): void { @@ -176,7 +176,7 @@ public function setFailed(?int $value): void { } /** - * Sets the inProgress property value. The inProgress property + * Sets the inProgress property value. The number of artifacts whose restoration is in progress. * @param int|null $value Value to set for the inProgress property. */ public function setInProgress(?int $value): void { @@ -192,7 +192,7 @@ public function setOdataType(?string $value): void { } /** - * Sets the total property value. The total property + * Sets the total property value. The number of artifacts present in the restore session. * @param int|null $value Value to set for the total property. */ public function setTotal(?int $value): void { diff --git a/src/Generated/Models/RestoreSessionBase.php b/src/Generated/Models/RestoreSessionBase.php index 345c23ec669..cccd61e818f 100644 --- a/src/Generated/Models/RestoreSessionBase.php +++ b/src/Generated/Models/RestoreSessionBase.php @@ -126,7 +126,7 @@ public function getLastModifiedDateTime(): ?DateTime { } /** - * Gets the restoreJobType property value. The restoreJobType property + * Gets the restoreJobType property value. Indicates whether the restore session was created normally or by a bulk job. * @return RestoreJobType|null */ public function getRestoreJobType(): ?RestoreJobType { @@ -138,7 +138,7 @@ public function getRestoreJobType(): ?RestoreJobType { } /** - * Gets the restoreSessionArtifactCount property value. The restoreSessionArtifactCount property + * Gets the restoreSessionArtifactCount property value. The number of metadata artifacts that belong to this restore session. * @return RestoreSessionArtifactCount|null */ public function getRestoreSessionArtifactCount(): ?RestoreSessionArtifactCount { @@ -227,7 +227,7 @@ public function setLastModifiedDateTime(?DateTime $value): void { } /** - * Sets the restoreJobType property value. The restoreJobType property + * Sets the restoreJobType property value. Indicates whether the restore session was created normally or by a bulk job. * @param RestoreJobType|null $value Value to set for the restoreJobType property. */ public function setRestoreJobType(?RestoreJobType $value): void { @@ -235,7 +235,7 @@ public function setRestoreJobType(?RestoreJobType $value): void { } /** - * Sets the restoreSessionArtifactCount property value. The restoreSessionArtifactCount property + * Sets the restoreSessionArtifactCount property value. The number of metadata artifacts that belong to this restore session. * @param RestoreSessionArtifactCount|null $value Value to set for the restoreSessionArtifactCount property. */ public function setRestoreSessionArtifactCount(?RestoreSessionArtifactCount $value): void { diff --git a/src/Generated/Models/WindowsDomainJoinConfiguration.php b/src/Generated/Models/WindowsDomainJoinConfiguration.php index 75d11378109..0fcbee9387c 100644 --- a/src/Generated/Models/WindowsDomainJoinConfiguration.php +++ b/src/Generated/Models/WindowsDomainJoinConfiguration.php @@ -81,7 +81,7 @@ public function getFieldDeserializers(): array { } /** - * Gets the networkAccessConfigurations property value. Reference to device configurations required for network connectivity + * Gets the networkAccessConfigurations property value. Reference to device configurations required for network connectivity. This collection can contain a maximum of 2 elements. * @return array|null */ public function getNetworkAccessConfigurations(): ?array { @@ -144,7 +144,7 @@ public function setComputerNameSuffixRandomCharCount(?int $value): void { } /** - * Sets the networkAccessConfigurations property value. Reference to device configurations required for network connectivity + * Sets the networkAccessConfigurations property value. Reference to device configurations required for network connectivity. This collection can contain a maximum of 2 elements. * @param array|null $value Value to set for the networkAccessConfigurations property. */ public function setNetworkAccessConfigurations(?array $value): void { diff --git a/src/Generated/Models/WindowsUniversalAppXAppAssignmentSettings.php b/src/Generated/Models/WindowsUniversalAppXAppAssignmentSettings.php index f39201d31d5..09549ae6756 100644 --- a/src/Generated/Models/WindowsUniversalAppXAppAssignmentSettings.php +++ b/src/Generated/Models/WindowsUniversalAppXAppAssignmentSettings.php @@ -40,7 +40,7 @@ public function getFieldDeserializers(): array { } /** - * Gets the useDeviceContext property value. Whether or not to use device execution context for Windows Universal AppX mobile app. + * Gets the useDeviceContext property value. If true, uses device execution context for Windows Universal AppX mobile app. Device-context install is not allowed when this type of app is targeted with Available intent. Defaults to false. * @return bool|null */ public function getUseDeviceContext(): ?bool { @@ -61,7 +61,7 @@ public function serialize(SerializationWriter $writer): void { } /** - * Sets the useDeviceContext property value. Whether or not to use device execution context for Windows Universal AppX mobile app. + * Sets the useDeviceContext property value. If true, uses device execution context for Windows Universal AppX mobile app. Device-context install is not allowed when this type of app is targeted with Available intent. Defaults to false. * @param bool|null $value Value to set for the useDeviceContext property. */ public function setUseDeviceContext(?bool $value): void { diff --git a/src/Generated/NetworkAccess/Connectivity/Branches/Item/ForwardingProfiles/Item/Policies/Item/PolicyLinkItemRequestBuilder.php b/src/Generated/NetworkAccess/Connectivity/Branches/Item/ForwardingProfiles/Item/Policies/Item/PolicyLinkItemRequestBuilder.php index 37ac4898cf2..0be17f485c5 100644 --- a/src/Generated/NetworkAccess/Connectivity/Branches/Item/ForwardingProfiles/Item/Policies/Item/PolicyLinkItemRequestBuilder.php +++ b/src/Generated/NetworkAccess/Connectivity/Branches/Item/ForwardingProfiles/Item/Policies/Item/PolicyLinkItemRequestBuilder.php @@ -53,7 +53,7 @@ public function delete(?PolicyLinkItemRequestBuilderDeleteRequestConfiguration $ } /** - * Traffic forwarding policies associated with this profile. + * The traffic forwarding policies associated with this profile. * @param PolicyLinkItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -100,7 +100,7 @@ public function toDeleteRequestInformation(?PolicyLinkItemRequestBuilderDeleteRe } /** - * Traffic forwarding policies associated with this profile. + * The traffic forwarding policies associated with this profile. * @param PolicyLinkItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/NetworkAccess/Connectivity/Branches/Item/ForwardingProfiles/Item/Policies/Item/PolicyLinkItemRequestBuilderGetQueryParameters.php b/src/Generated/NetworkAccess/Connectivity/Branches/Item/ForwardingProfiles/Item/Policies/Item/PolicyLinkItemRequestBuilderGetQueryParameters.php index d22a7a5e509..ff9e19a6d52 100644 --- a/src/Generated/NetworkAccess/Connectivity/Branches/Item/ForwardingProfiles/Item/Policies/Item/PolicyLinkItemRequestBuilderGetQueryParameters.php +++ b/src/Generated/NetworkAccess/Connectivity/Branches/Item/ForwardingProfiles/Item/Policies/Item/PolicyLinkItemRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Traffic forwarding policies associated with this profile. + * The traffic forwarding policies associated with this profile. */ class PolicyLinkItemRequestBuilderGetQueryParameters { diff --git a/src/Generated/NetworkAccess/Connectivity/Branches/Item/ForwardingProfiles/Item/Policies/PoliciesRequestBuilder.php b/src/Generated/NetworkAccess/Connectivity/Branches/Item/ForwardingProfiles/Item/Policies/PoliciesRequestBuilder.php index ed8f3a5e7d7..c713658e03b 100644 --- a/src/Generated/NetworkAccess/Connectivity/Branches/Item/ForwardingProfiles/Item/Policies/PoliciesRequestBuilder.php +++ b/src/Generated/NetworkAccess/Connectivity/Branches/Item/ForwardingProfiles/Item/Policies/PoliciesRequestBuilder.php @@ -52,7 +52,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Traffic forwarding policies associated with this profile. + * The traffic forwarding policies associated with this profile. * @param PoliciesRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -81,7 +81,7 @@ public function post(PolicyLink $body, ?PoliciesRequestBuilderPostRequestConfigu } /** - * Traffic forwarding policies associated with this profile. + * The traffic forwarding policies associated with this profile. * @param PoliciesRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/NetworkAccess/Connectivity/Branches/Item/ForwardingProfiles/Item/Policies/PoliciesRequestBuilderGetQueryParameters.php b/src/Generated/NetworkAccess/Connectivity/Branches/Item/ForwardingProfiles/Item/Policies/PoliciesRequestBuilderGetQueryParameters.php index 05ba8d084a8..93359937d98 100644 --- a/src/Generated/NetworkAccess/Connectivity/Branches/Item/ForwardingProfiles/Item/Policies/PoliciesRequestBuilderGetQueryParameters.php +++ b/src/Generated/NetworkAccess/Connectivity/Branches/Item/ForwardingProfiles/Item/Policies/PoliciesRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Traffic forwarding policies associated with this profile. + * The traffic forwarding policies associated with this profile. */ class PoliciesRequestBuilderGetQueryParameters { diff --git a/src/Generated/NetworkAccess/Connectivity/RemoteNetworks/Item/ForwardingProfiles/Item/Policies/Item/PolicyLinkItemRequestBuilder.php b/src/Generated/NetworkAccess/Connectivity/RemoteNetworks/Item/ForwardingProfiles/Item/Policies/Item/PolicyLinkItemRequestBuilder.php index 5d1217067b6..c725a24bbc0 100644 --- a/src/Generated/NetworkAccess/Connectivity/RemoteNetworks/Item/ForwardingProfiles/Item/Policies/Item/PolicyLinkItemRequestBuilder.php +++ b/src/Generated/NetworkAccess/Connectivity/RemoteNetworks/Item/ForwardingProfiles/Item/Policies/Item/PolicyLinkItemRequestBuilder.php @@ -53,7 +53,7 @@ public function delete(?PolicyLinkItemRequestBuilderDeleteRequestConfiguration $ } /** - * Traffic forwarding policies associated with this profile. + * The traffic forwarding policies associated with this profile. * @param PolicyLinkItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -100,7 +100,7 @@ public function toDeleteRequestInformation(?PolicyLinkItemRequestBuilderDeleteRe } /** - * Traffic forwarding policies associated with this profile. + * The traffic forwarding policies associated with this profile. * @param PolicyLinkItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/NetworkAccess/Connectivity/RemoteNetworks/Item/ForwardingProfiles/Item/Policies/Item/PolicyLinkItemRequestBuilderGetQueryParameters.php b/src/Generated/NetworkAccess/Connectivity/RemoteNetworks/Item/ForwardingProfiles/Item/Policies/Item/PolicyLinkItemRequestBuilderGetQueryParameters.php index 52004d63b6a..b7d5a77f30b 100644 --- a/src/Generated/NetworkAccess/Connectivity/RemoteNetworks/Item/ForwardingProfiles/Item/Policies/Item/PolicyLinkItemRequestBuilderGetQueryParameters.php +++ b/src/Generated/NetworkAccess/Connectivity/RemoteNetworks/Item/ForwardingProfiles/Item/Policies/Item/PolicyLinkItemRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Traffic forwarding policies associated with this profile. + * The traffic forwarding policies associated with this profile. */ class PolicyLinkItemRequestBuilderGetQueryParameters { diff --git a/src/Generated/NetworkAccess/Connectivity/RemoteNetworks/Item/ForwardingProfiles/Item/Policies/PoliciesRequestBuilder.php b/src/Generated/NetworkAccess/Connectivity/RemoteNetworks/Item/ForwardingProfiles/Item/Policies/PoliciesRequestBuilder.php index f598860ff33..443802cf806 100644 --- a/src/Generated/NetworkAccess/Connectivity/RemoteNetworks/Item/ForwardingProfiles/Item/Policies/PoliciesRequestBuilder.php +++ b/src/Generated/NetworkAccess/Connectivity/RemoteNetworks/Item/ForwardingProfiles/Item/Policies/PoliciesRequestBuilder.php @@ -52,7 +52,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Traffic forwarding policies associated with this profile. + * The traffic forwarding policies associated with this profile. * @param PoliciesRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -81,7 +81,7 @@ public function post(PolicyLink $body, ?PoliciesRequestBuilderPostRequestConfigu } /** - * Traffic forwarding policies associated with this profile. + * The traffic forwarding policies associated with this profile. * @param PoliciesRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/NetworkAccess/Connectivity/RemoteNetworks/Item/ForwardingProfiles/Item/Policies/PoliciesRequestBuilderGetQueryParameters.php b/src/Generated/NetworkAccess/Connectivity/RemoteNetworks/Item/ForwardingProfiles/Item/Policies/PoliciesRequestBuilderGetQueryParameters.php index 66baafab832..e117dca6749 100644 --- a/src/Generated/NetworkAccess/Connectivity/RemoteNetworks/Item/ForwardingProfiles/Item/Policies/PoliciesRequestBuilderGetQueryParameters.php +++ b/src/Generated/NetworkAccess/Connectivity/RemoteNetworks/Item/ForwardingProfiles/Item/Policies/PoliciesRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Traffic forwarding policies associated with this profile. + * The traffic forwarding policies associated with this profile. */ class PoliciesRequestBuilderGetQueryParameters { diff --git a/src/Generated/NetworkAccess/Connectivity/RemoteNetworks/Item/RemoteNetworkItemRequestBuilder.php b/src/Generated/NetworkAccess/Connectivity/RemoteNetworks/Item/RemoteNetworkItemRequestBuilder.php index f01600c6a01..f1cabb14520 100644 --- a/src/Generated/NetworkAccess/Connectivity/RemoteNetworks/Item/RemoteNetworkItemRequestBuilder.php +++ b/src/Generated/NetworkAccess/Connectivity/RemoteNetworks/Item/RemoteNetworkItemRequestBuilder.php @@ -69,7 +69,7 @@ public function delete(?RemoteNetworkItemRequestBuilderDeleteRequestConfiguratio } /** - * Represent locations, such as branches, that are connected to Global Secure Access services through an IPsec tunnel. + * The locations, such as branches, that are connected to Global Secure Access services through an IPsec tunnel. * @param RemoteNetworkItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -116,7 +116,7 @@ public function toDeleteRequestInformation(?RemoteNetworkItemRequestBuilderDelet } /** - * Represent locations, such as branches, that are connected to Global Secure Access services through an IPsec tunnel. + * The locations, such as branches, that are connected to Global Secure Access services through an IPsec tunnel. * @param RemoteNetworkItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/NetworkAccess/Connectivity/RemoteNetworks/Item/RemoteNetworkItemRequestBuilderGetQueryParameters.php b/src/Generated/NetworkAccess/Connectivity/RemoteNetworks/Item/RemoteNetworkItemRequestBuilderGetQueryParameters.php index 8f2d4c86eb9..90645964bf0 100644 --- a/src/Generated/NetworkAccess/Connectivity/RemoteNetworks/Item/RemoteNetworkItemRequestBuilderGetQueryParameters.php +++ b/src/Generated/NetworkAccess/Connectivity/RemoteNetworks/Item/RemoteNetworkItemRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Represent locations, such as branches, that are connected to Global Secure Access services through an IPsec tunnel. + * The locations, such as branches, that are connected to Global Secure Access services through an IPsec tunnel. */ class RemoteNetworkItemRequestBuilderGetQueryParameters { diff --git a/src/Generated/NetworkAccess/Connectivity/RemoteNetworks/RemoteNetworksRequestBuilder.php b/src/Generated/NetworkAccess/Connectivity/RemoteNetworks/RemoteNetworksRequestBuilder.php index cd211fa5a00..13a822b3eeb 100644 --- a/src/Generated/NetworkAccess/Connectivity/RemoteNetworks/RemoteNetworksRequestBuilder.php +++ b/src/Generated/NetworkAccess/Connectivity/RemoteNetworks/RemoteNetworksRequestBuilder.php @@ -52,7 +52,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Represent locations, such as branches, that are connected to Global Secure Access services through an IPsec tunnel. + * The locations, such as branches, that are connected to Global Secure Access services through an IPsec tunnel. * @param RemoteNetworksRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -82,7 +82,7 @@ public function post(RemoteNetwork $body, ?RemoteNetworksRequestBuilderPostReque } /** - * Represent locations, such as branches, that are connected to Global Secure Access services through an IPsec tunnel. + * The locations, such as branches, that are connected to Global Secure Access services through an IPsec tunnel. * @param RemoteNetworksRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/NetworkAccess/Connectivity/RemoteNetworks/RemoteNetworksRequestBuilderGetQueryParameters.php b/src/Generated/NetworkAccess/Connectivity/RemoteNetworks/RemoteNetworksRequestBuilderGetQueryParameters.php index d393f4bf234..821b3e8adb8 100644 --- a/src/Generated/NetworkAccess/Connectivity/RemoteNetworks/RemoteNetworksRequestBuilderGetQueryParameters.php +++ b/src/Generated/NetworkAccess/Connectivity/RemoteNetworks/RemoteNetworksRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Represent locations, such as branches, that are connected to Global Secure Access services through an IPsec tunnel. + * The locations, such as branches, that are connected to Global Secure Access services through an IPsec tunnel. */ class RemoteNetworksRequestBuilderGetQueryParameters { diff --git a/src/Generated/NetworkAccess/FilteringProfiles/Item/Policies/Item/PolicyLinkItemRequestBuilder.php b/src/Generated/NetworkAccess/FilteringProfiles/Item/Policies/Item/PolicyLinkItemRequestBuilder.php index 757d3c155dd..76dee971214 100644 --- a/src/Generated/NetworkAccess/FilteringProfiles/Item/Policies/Item/PolicyLinkItemRequestBuilder.php +++ b/src/Generated/NetworkAccess/FilteringProfiles/Item/Policies/Item/PolicyLinkItemRequestBuilder.php @@ -53,7 +53,7 @@ public function delete(?PolicyLinkItemRequestBuilderDeleteRequestConfiguration $ } /** - * Traffic forwarding policies associated with this profile. + * The traffic forwarding policies associated with this profile. * @param PolicyLinkItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -100,7 +100,7 @@ public function toDeleteRequestInformation(?PolicyLinkItemRequestBuilderDeleteRe } /** - * Traffic forwarding policies associated with this profile. + * The traffic forwarding policies associated with this profile. * @param PolicyLinkItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/NetworkAccess/FilteringProfiles/Item/Policies/Item/PolicyLinkItemRequestBuilderGetQueryParameters.php b/src/Generated/NetworkAccess/FilteringProfiles/Item/Policies/Item/PolicyLinkItemRequestBuilderGetQueryParameters.php index 83daeb7753c..0e6ef1bfadb 100644 --- a/src/Generated/NetworkAccess/FilteringProfiles/Item/Policies/Item/PolicyLinkItemRequestBuilderGetQueryParameters.php +++ b/src/Generated/NetworkAccess/FilteringProfiles/Item/Policies/Item/PolicyLinkItemRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Traffic forwarding policies associated with this profile. + * The traffic forwarding policies associated with this profile. */ class PolicyLinkItemRequestBuilderGetQueryParameters { diff --git a/src/Generated/NetworkAccess/FilteringProfiles/Item/Policies/PoliciesRequestBuilder.php b/src/Generated/NetworkAccess/FilteringProfiles/Item/Policies/PoliciesRequestBuilder.php index 8c46bd1dda2..bf1a2f2d6b4 100644 --- a/src/Generated/NetworkAccess/FilteringProfiles/Item/Policies/PoliciesRequestBuilder.php +++ b/src/Generated/NetworkAccess/FilteringProfiles/Item/Policies/PoliciesRequestBuilder.php @@ -52,7 +52,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Traffic forwarding policies associated with this profile. + * The traffic forwarding policies associated with this profile. * @param PoliciesRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -81,7 +81,7 @@ public function post(PolicyLink $body, ?PoliciesRequestBuilderPostRequestConfigu } /** - * Traffic forwarding policies associated with this profile. + * The traffic forwarding policies associated with this profile. * @param PoliciesRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/NetworkAccess/FilteringProfiles/Item/Policies/PoliciesRequestBuilderGetQueryParameters.php b/src/Generated/NetworkAccess/FilteringProfiles/Item/Policies/PoliciesRequestBuilderGetQueryParameters.php index cd97e417974..eb446a142af 100644 --- a/src/Generated/NetworkAccess/FilteringProfiles/Item/Policies/PoliciesRequestBuilderGetQueryParameters.php +++ b/src/Generated/NetworkAccess/FilteringProfiles/Item/Policies/PoliciesRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Traffic forwarding policies associated with this profile. + * The traffic forwarding policies associated with this profile. */ class PoliciesRequestBuilderGetQueryParameters { diff --git a/src/Generated/Policies/CrossTenantAccessPolicy/Partners/Item/IdentitySynchronization/IdentitySynchronizationRequestBuilder.php b/src/Generated/Policies/CrossTenantAccessPolicy/Partners/Item/IdentitySynchronization/IdentitySynchronizationRequestBuilder.php index 5d0827d4b23..db385e2598f 100644 --- a/src/Generated/Policies/CrossTenantAccessPolicy/Partners/Item/IdentitySynchronization/IdentitySynchronizationRequestBuilder.php +++ b/src/Generated/Policies/CrossTenantAccessPolicy/Partners/Item/IdentitySynchronization/IdentitySynchronizationRequestBuilder.php @@ -61,12 +61,12 @@ public function get(?IdentitySynchronizationRequestBuilderGetRequestConfiguratio } /** - * Create a cross-tenant user synchronization policy for a partner-specific configuration. + * Update the user synchronization policy of a partner-specific configuration. * @param CrossTenantIdentitySyncPolicyPartner $body The request body * @param IdentitySynchronizationRequestBuilderPutRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception - * @link https://learn.microsoft.com/graph/api/crosstenantaccesspolicyconfigurationpartner-put-identitysynchronization?view=graph-rest-beta Find more info here + * @link https://learn.microsoft.com/graph/api/crosstenantidentitysyncpolicypartner-update?view=graph-rest-beta Find more info here */ public function put(CrossTenantIdentitySyncPolicyPartner $body, ?IdentitySynchronizationRequestBuilderPutRequestConfiguration $requestConfiguration = null): Promise { $requestInfo = $this->toPutRequestInformation($body, $requestConfiguration); @@ -116,7 +116,7 @@ public function toGetRequestInformation(?IdentitySynchronizationRequestBuilderGe } /** - * Create a cross-tenant user synchronization policy for a partner-specific configuration. + * Update the user synchronization policy of a partner-specific configuration. * @param CrossTenantIdentitySyncPolicyPartner $body The request body * @param IdentitySynchronizationRequestBuilderPutRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation diff --git a/src/Generated/Policies/FederatedTokenValidationPolicy/FederatedTokenValidationPolicyRequestBuilder.php b/src/Generated/Policies/FederatedTokenValidationPolicy/FederatedTokenValidationPolicyRequestBuilder.php index 5457114609c..b17b7567cb4 100644 --- a/src/Generated/Policies/FederatedTokenValidationPolicy/FederatedTokenValidationPolicyRequestBuilder.php +++ b/src/Generated/Policies/FederatedTokenValidationPolicy/FederatedTokenValidationPolicyRequestBuilder.php @@ -45,11 +45,11 @@ public function delete(?FederatedTokenValidationPolicyRequestBuilderDeleteReques } /** - * Get a list of the federatedTokenValidationPolicy objects and their properties. + * Read the properties and relationships of a federatedTokenValidationPolicy object. * @param FederatedTokenValidationPolicyRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception - * @link https://learn.microsoft.com/graph/api/policyroot-list-federatedtokenvalidationpolicy?view=graph-rest-beta Find more info here + * @link https://learn.microsoft.com/graph/api/federatedtokenvalidationpolicy-get?view=graph-rest-beta Find more info here */ public function get(?FederatedTokenValidationPolicyRequestBuilderGetRequestConfiguration $requestConfiguration = null): Promise { $requestInfo = $this->toGetRequestInformation($requestConfiguration); @@ -94,7 +94,7 @@ public function toDeleteRequestInformation(?FederatedTokenValidationPolicyReques } /** - * Get a list of the federatedTokenValidationPolicy objects and their properties. + * Read the properties and relationships of a federatedTokenValidationPolicy object. * @param FederatedTokenValidationPolicyRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Policies/FederatedTokenValidationPolicy/FederatedTokenValidationPolicyRequestBuilderGetQueryParameters.php b/src/Generated/Policies/FederatedTokenValidationPolicy/FederatedTokenValidationPolicyRequestBuilderGetQueryParameters.php index 76cdbb96833..f91cde98490 100644 --- a/src/Generated/Policies/FederatedTokenValidationPolicy/FederatedTokenValidationPolicyRequestBuilderGetQueryParameters.php +++ b/src/Generated/Policies/FederatedTokenValidationPolicy/FederatedTokenValidationPolicyRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a list of the federatedTokenValidationPolicy objects and their properties. + * Read the properties and relationships of a federatedTokenValidationPolicy object. */ class FederatedTokenValidationPolicyRequestBuilderGetQueryParameters { diff --git a/src/Generated/RiskDetections/RiskDetectionsRequestBuilder.php b/src/Generated/RiskDetections/RiskDetectionsRequestBuilder.php index a0d22a4ca46..ca1e7a8c651 100644 --- a/src/Generated/RiskDetections/RiskDetectionsRequestBuilder.php +++ b/src/Generated/RiskDetections/RiskDetectionsRequestBuilder.php @@ -44,11 +44,11 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Retrieve the properties of a riskDetection object. + * Retrieve the properties of a collection of riskDetection objects. * @param RiskDetectionsRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception - * @link https://learn.microsoft.com/graph/api/riskdetection-get?view=graph-rest-beta Find more info here + * @link https://learn.microsoft.com/graph/api/riskdetection-list?view=graph-rest-beta Find more info here */ public function get(?RiskDetectionsRequestBuilderGetRequestConfiguration $requestConfiguration = null): Promise { $requestInfo = $this->toGetRequestInformation($requestConfiguration); @@ -74,7 +74,7 @@ public function post(RiskDetection $body, ?RiskDetectionsRequestBuilderPostReque } /** - * Retrieve the properties of a riskDetection object. + * Retrieve the properties of a collection of riskDetection objects. * @param RiskDetectionsRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/RiskDetections/RiskDetectionsRequestBuilderGetQueryParameters.php b/src/Generated/RiskDetections/RiskDetectionsRequestBuilderGetQueryParameters.php index 8c6152e8124..1464dc22797 100644 --- a/src/Generated/RiskDetections/RiskDetectionsRequestBuilderGetQueryParameters.php +++ b/src/Generated/RiskDetections/RiskDetectionsRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Retrieve the properties of a riskDetection object. + * Retrieve the properties of a collection of riskDetection objects. */ class RiskDetectionsRequestBuilderGetQueryParameters { diff --git a/src/Generated/ServicePrincipals/Item/ClaimsPolicy/ClaimsPolicyRequestBuilder.php b/src/Generated/ServicePrincipals/Item/ClaimsPolicy/ClaimsPolicyRequestBuilder.php index a058f410f22..9da3a24d885 100644 --- a/src/Generated/ServicePrincipals/Item/ClaimsPolicy/ClaimsPolicyRequestBuilder.php +++ b/src/Generated/ServicePrincipals/Item/ClaimsPolicy/ClaimsPolicyRequestBuilder.php @@ -46,12 +46,12 @@ public function get(?ClaimsPolicyRequestBuilderGetRequestConfiguration $requestC } /** - * Create a new customClaimsPolicy object if it doesn't exist, or replace an existing one. + * Update a customClaimsPolicy object. * @param CustomClaimsPolicy $body The request body * @param ClaimsPolicyRequestBuilderPatchRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception - * @link https://learn.microsoft.com/graph/api/serviceprincipal-put-claimspolicy?view=graph-rest-beta Find more info here + * @link https://learn.microsoft.com/graph/api/customclaimspolicy-update?view=graph-rest-beta Find more info here */ public function patch(CustomClaimsPolicy $body, ?ClaimsPolicyRequestBuilderPatchRequestConfiguration $requestConfiguration = null): Promise { $requestInfo = $this->toPatchRequestInformation($body, $requestConfiguration); @@ -62,12 +62,12 @@ public function patch(CustomClaimsPolicy $body, ?ClaimsPolicyRequestBuilderPatch } /** - * Create a new customClaimsPolicy object if it doesn't exist, or replace an existing one. + * Update a customClaimsPolicy object. * @param CustomClaimsPolicy $body The request body * @param ClaimsPolicyRequestBuilderPutRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception - * @link https://learn.microsoft.com/graph/api/serviceprincipal-put-claimspolicy?view=graph-rest-beta Find more info here + * @link https://learn.microsoft.com/graph/api/customclaimspolicy-update?view=graph-rest-beta Find more info here */ public function put(CustomClaimsPolicy $body, ?ClaimsPolicyRequestBuilderPutRequestConfiguration $requestConfiguration = null): Promise { $requestInfo = $this->toPutRequestInformation($body, $requestConfiguration); @@ -99,7 +99,7 @@ public function toGetRequestInformation(?ClaimsPolicyRequestBuilderGetRequestCon } /** - * Create a new customClaimsPolicy object if it doesn't exist, or replace an existing one. + * Update a customClaimsPolicy object. * @param CustomClaimsPolicy $body The request body * @param ClaimsPolicyRequestBuilderPatchRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation @@ -119,7 +119,7 @@ public function toPatchRequestInformation(CustomClaimsPolicy $body, ?ClaimsPolic } /** - * Create a new customClaimsPolicy object if it doesn't exist, or replace an existing one. + * Update a customClaimsPolicy object. * @param CustomClaimsPolicy $body The request body * @param ClaimsPolicyRequestBuilderPutRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation diff --git a/src/Generated/Sites/Item/Onenote/Notebooks/Item/NotebookItemRequestBuilder.php b/src/Generated/Sites/Item/Onenote/Notebooks/Item/NotebookItemRequestBuilder.php index c555bd7347e..bc42069093c 100644 --- a/src/Generated/Sites/Item/Onenote/Notebooks/Item/NotebookItemRequestBuilder.php +++ b/src/Generated/Sites/Item/Onenote/Notebooks/Item/NotebookItemRequestBuilder.php @@ -69,7 +69,7 @@ public function delete(?NotebookItemRequestBuilderDeleteRequestConfiguration $re } /** - * The collection of OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The collection of OneNote notebooks that the user or group owns. Read-only. Nullable. * @param NotebookItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -116,7 +116,7 @@ public function toDeleteRequestInformation(?NotebookItemRequestBuilderDeleteRequ } /** - * The collection of OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The collection of OneNote notebooks that the user or group owns. Read-only. Nullable. * @param NotebookItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Sites/Item/Onenote/Notebooks/Item/NotebookItemRequestBuilderGetQueryParameters.php b/src/Generated/Sites/Item/Onenote/Notebooks/Item/NotebookItemRequestBuilderGetQueryParameters.php index 294cad64322..2bd23799eea 100644 --- a/src/Generated/Sites/Item/Onenote/Notebooks/Item/NotebookItemRequestBuilderGetQueryParameters.php +++ b/src/Generated/Sites/Item/Onenote/Notebooks/Item/NotebookItemRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * The collection of OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The collection of OneNote notebooks that the user or group owns. Read-only. Nullable. */ class NotebookItemRequestBuilderGetQueryParameters { diff --git a/src/Generated/Sites/Item/Onenote/Notebooks/NotebooksRequestBuilder.php b/src/Generated/Sites/Item/Onenote/Notebooks/NotebooksRequestBuilder.php index 5056b473f88..51f60d740bf 100644 --- a/src/Generated/Sites/Item/Onenote/Notebooks/NotebooksRequestBuilder.php +++ b/src/Generated/Sites/Item/Onenote/Notebooks/NotebooksRequestBuilder.php @@ -61,7 +61,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * The collection of OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The collection of OneNote notebooks that the user or group owns. Read-only. Nullable. * @param NotebooksRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -99,7 +99,7 @@ public function post(Notebook $body, ?NotebooksRequestBuilderPostRequestConfigur } /** - * The collection of OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The collection of OneNote notebooks that the user or group owns. Read-only. Nullable. * @param NotebooksRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Sites/Item/Onenote/Notebooks/NotebooksRequestBuilderGetQueryParameters.php b/src/Generated/Sites/Item/Onenote/Notebooks/NotebooksRequestBuilderGetQueryParameters.php index 81cf84b3c2b..e4329269b62 100644 --- a/src/Generated/Sites/Item/Onenote/Notebooks/NotebooksRequestBuilderGetQueryParameters.php +++ b/src/Generated/Sites/Item/Onenote/Notebooks/NotebooksRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * The collection of OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The collection of OneNote notebooks that the user or group owns. Read-only. Nullable. */ class NotebooksRequestBuilderGetQueryParameters { diff --git a/src/Generated/Sites/Item/Onenote/Pages/Item/OnenotePageItemRequestBuilder.php b/src/Generated/Sites/Item/Onenote/Pages/Item/OnenotePageItemRequestBuilder.php index b3feac741e4..d2d03d9963f 100644 --- a/src/Generated/Sites/Item/Onenote/Pages/Item/OnenotePageItemRequestBuilder.php +++ b/src/Generated/Sites/Item/Onenote/Pages/Item/OnenotePageItemRequestBuilder.php @@ -93,7 +93,7 @@ public function delete(?OnenotePageItemRequestBuilderDeleteRequestConfiguration } /** - * The pages in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The pages in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @param OnenotePageItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -140,7 +140,7 @@ public function toDeleteRequestInformation(?OnenotePageItemRequestBuilderDeleteR } /** - * The pages in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The pages in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @param OnenotePageItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Sites/Item/Onenote/Pages/Item/OnenotePageItemRequestBuilderGetQueryParameters.php b/src/Generated/Sites/Item/Onenote/Pages/Item/OnenotePageItemRequestBuilderGetQueryParameters.php index 242bf1bdadf..a3e01254409 100644 --- a/src/Generated/Sites/Item/Onenote/Pages/Item/OnenotePageItemRequestBuilderGetQueryParameters.php +++ b/src/Generated/Sites/Item/Onenote/Pages/Item/OnenotePageItemRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * The pages in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The pages in all OneNote notebooks that the user or group owns. Read-only. Nullable. */ class OnenotePageItemRequestBuilderGetQueryParameters { diff --git a/src/Generated/Sites/Item/Onenote/Pages/PagesRequestBuilder.php b/src/Generated/Sites/Item/Onenote/Pages/PagesRequestBuilder.php index bd814ff3c45..601bd58fec7 100644 --- a/src/Generated/Sites/Item/Onenote/Pages/PagesRequestBuilder.php +++ b/src/Generated/Sites/Item/Onenote/Pages/PagesRequestBuilder.php @@ -52,7 +52,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * The pages in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The pages in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @param PagesRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -81,7 +81,7 @@ public function post(OnenotePage $body, ?PagesRequestBuilderPostRequestConfigura } /** - * The pages in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The pages in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @param PagesRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Sites/Item/Onenote/Pages/PagesRequestBuilderGetQueryParameters.php b/src/Generated/Sites/Item/Onenote/Pages/PagesRequestBuilderGetQueryParameters.php index 5e3ebcaddf4..a586a0973ab 100644 --- a/src/Generated/Sites/Item/Onenote/Pages/PagesRequestBuilderGetQueryParameters.php +++ b/src/Generated/Sites/Item/Onenote/Pages/PagesRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * The pages in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The pages in all OneNote notebooks that the user or group owns. Read-only. Nullable. */ class PagesRequestBuilderGetQueryParameters { diff --git a/src/Generated/Sites/Item/Onenote/SectionGroups/Item/SectionGroupItemRequestBuilder.php b/src/Generated/Sites/Item/Onenote/SectionGroups/Item/SectionGroupItemRequestBuilder.php index 404664e1b0e..b06b0026143 100644 --- a/src/Generated/Sites/Item/Onenote/SectionGroups/Item/SectionGroupItemRequestBuilder.php +++ b/src/Generated/Sites/Item/Onenote/SectionGroups/Item/SectionGroupItemRequestBuilder.php @@ -77,7 +77,7 @@ public function delete(?SectionGroupItemRequestBuilderDeleteRequestConfiguration } /** - * The section groups in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The section groups in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @param SectionGroupItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -124,7 +124,7 @@ public function toDeleteRequestInformation(?SectionGroupItemRequestBuilderDelete } /** - * The section groups in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The section groups in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @param SectionGroupItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Sites/Item/Onenote/SectionGroups/Item/SectionGroupItemRequestBuilderGetQueryParameters.php b/src/Generated/Sites/Item/Onenote/SectionGroups/Item/SectionGroupItemRequestBuilderGetQueryParameters.php index 5260e0f9acb..d760c9e2011 100644 --- a/src/Generated/Sites/Item/Onenote/SectionGroups/Item/SectionGroupItemRequestBuilderGetQueryParameters.php +++ b/src/Generated/Sites/Item/Onenote/SectionGroups/Item/SectionGroupItemRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * The section groups in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The section groups in all OneNote notebooks that the user or group owns. Read-only. Nullable. */ class SectionGroupItemRequestBuilderGetQueryParameters { diff --git a/src/Generated/Sites/Item/Onenote/SectionGroups/SectionGroupsRequestBuilder.php b/src/Generated/Sites/Item/Onenote/SectionGroups/SectionGroupsRequestBuilder.php index 3e6ea0152fc..f750ad2c089 100644 --- a/src/Generated/Sites/Item/Onenote/SectionGroups/SectionGroupsRequestBuilder.php +++ b/src/Generated/Sites/Item/Onenote/SectionGroups/SectionGroupsRequestBuilder.php @@ -52,7 +52,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * The section groups in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The section groups in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @param SectionGroupsRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -81,7 +81,7 @@ public function post(SectionGroup $body, ?SectionGroupsRequestBuilderPostRequest } /** - * The section groups in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The section groups in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @param SectionGroupsRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Sites/Item/Onenote/SectionGroups/SectionGroupsRequestBuilderGetQueryParameters.php b/src/Generated/Sites/Item/Onenote/SectionGroups/SectionGroupsRequestBuilderGetQueryParameters.php index 4aca9cfbb8f..c9a619c3863 100644 --- a/src/Generated/Sites/Item/Onenote/SectionGroups/SectionGroupsRequestBuilderGetQueryParameters.php +++ b/src/Generated/Sites/Item/Onenote/SectionGroups/SectionGroupsRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * The section groups in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The section groups in all OneNote notebooks that the user or group owns. Read-only. Nullable. */ class SectionGroupsRequestBuilderGetQueryParameters { diff --git a/src/Generated/Sites/Item/Onenote/Sections/Item/OnenoteSectionItemRequestBuilder.php b/src/Generated/Sites/Item/Onenote/Sections/Item/OnenoteSectionItemRequestBuilder.php index 82ac8790992..8454a6d22b7 100644 --- a/src/Generated/Sites/Item/Onenote/Sections/Item/OnenoteSectionItemRequestBuilder.php +++ b/src/Generated/Sites/Item/Onenote/Sections/Item/OnenoteSectionItemRequestBuilder.php @@ -85,7 +85,7 @@ public function delete(?OnenoteSectionItemRequestBuilderDeleteRequestConfigurati } /** - * The sections in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The sections in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @param OnenoteSectionItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -132,7 +132,7 @@ public function toDeleteRequestInformation(?OnenoteSectionItemRequestBuilderDele } /** - * The sections in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The sections in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @param OnenoteSectionItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Sites/Item/Onenote/Sections/Item/OnenoteSectionItemRequestBuilderGetQueryParameters.php b/src/Generated/Sites/Item/Onenote/Sections/Item/OnenoteSectionItemRequestBuilderGetQueryParameters.php index 62cdfd8ef72..11aa0cd031e 100644 --- a/src/Generated/Sites/Item/Onenote/Sections/Item/OnenoteSectionItemRequestBuilderGetQueryParameters.php +++ b/src/Generated/Sites/Item/Onenote/Sections/Item/OnenoteSectionItemRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * The sections in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The sections in all OneNote notebooks that the user or group owns. Read-only. Nullable. */ class OnenoteSectionItemRequestBuilderGetQueryParameters { diff --git a/src/Generated/Sites/Item/Onenote/Sections/SectionsRequestBuilder.php b/src/Generated/Sites/Item/Onenote/Sections/SectionsRequestBuilder.php index fb5d6191fde..89b28b1a054 100644 --- a/src/Generated/Sites/Item/Onenote/Sections/SectionsRequestBuilder.php +++ b/src/Generated/Sites/Item/Onenote/Sections/SectionsRequestBuilder.php @@ -52,7 +52,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * The sections in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The sections in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @param SectionsRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -81,7 +81,7 @@ public function post(OnenoteSection $body, ?SectionsRequestBuilderPostRequestCon } /** - * The sections in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The sections in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @param SectionsRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Sites/Item/Onenote/Sections/SectionsRequestBuilderGetQueryParameters.php b/src/Generated/Sites/Item/Onenote/Sections/SectionsRequestBuilderGetQueryParameters.php index d86305ef9ae..871197315e4 100644 --- a/src/Generated/Sites/Item/Onenote/Sections/SectionsRequestBuilderGetQueryParameters.php +++ b/src/Generated/Sites/Item/Onenote/Sections/SectionsRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * The sections in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The sections in all OneNote notebooks that the user or group owns. Read-only. Nullable. */ class SectionsRequestBuilderGetQueryParameters { diff --git a/src/Generated/Sites/Item/Pages/PagesRequestBuilder.php b/src/Generated/Sites/Item/Pages/PagesRequestBuilder.php index 889bc2e9733..6d3f6bee76d 100644 --- a/src/Generated/Sites/Item/Pages/PagesRequestBuilder.php +++ b/src/Generated/Sites/Item/Pages/PagesRequestBuilder.php @@ -75,12 +75,12 @@ public function get(?PagesRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Create a new sitePage in the site pages list in a site. + * Create a new newsLinkPage in the site pages list of a site. * @param BaseSitePage $body The request body * @param PagesRequestBuilderPostRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception - * @link https://learn.microsoft.com/graph/api/sitepage-create?view=graph-rest-beta Find more info here + * @link https://learn.microsoft.com/graph/api/newslinkpage-create?view=graph-rest-beta Find more info here */ public function post(BaseSitePage $body, ?PagesRequestBuilderPostRequestConfiguration $requestConfiguration = null): Promise { $requestInfo = $this->toPostRequestInformation($body, $requestConfiguration); @@ -112,7 +112,7 @@ public function toGetRequestInformation(?PagesRequestBuilderGetRequestConfigurat } /** - * Create a new sitePage in the site pages list in a site. + * Create a new newsLinkPage in the site pages list of a site. * @param BaseSitePage $body The request body * @param PagesRequestBuilderPostRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation diff --git a/src/Generated/Solutions/BackupRestore/OneDriveForBusinessProtectionPolicies/Item/DriveProtectionUnits/Item/DriveProtectionUnitItemRequestBuilder.php b/src/Generated/Solutions/BackupRestore/OneDriveForBusinessProtectionPolicies/Item/DriveProtectionUnits/Item/DriveProtectionUnitItemRequestBuilder.php index 9787d7c9446..28b254149e3 100644 --- a/src/Generated/Solutions/BackupRestore/OneDriveForBusinessProtectionPolicies/Item/DriveProtectionUnits/Item/DriveProtectionUnitItemRequestBuilder.php +++ b/src/Generated/Solutions/BackupRestore/OneDriveForBusinessProtectionPolicies/Item/DriveProtectionUnits/Item/DriveProtectionUnitItemRequestBuilder.php @@ -31,7 +31,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Contains the protection units associated with a OneDrive for Business protection policy. + * Contains the protection units associated with a OneDrive for Work or School protection policy. * @param DriveProtectionUnitItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DriveProtectionUnitItemRequestBuilderGetRequestConfiguratio } /** - * Contains the protection units associated with a OneDrive for Business protection policy. + * Contains the protection units associated with a OneDrive for Work or School protection policy. * @param DriveProtectionUnitItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Solutions/BackupRestore/OneDriveForBusinessProtectionPolicies/Item/DriveProtectionUnits/Item/DriveProtectionUnitItemRequestBuilderGetQueryParameters.php b/src/Generated/Solutions/BackupRestore/OneDriveForBusinessProtectionPolicies/Item/DriveProtectionUnits/Item/DriveProtectionUnitItemRequestBuilderGetQueryParameters.php index a2123651cc6..287caea3490 100644 --- a/src/Generated/Solutions/BackupRestore/OneDriveForBusinessProtectionPolicies/Item/DriveProtectionUnits/Item/DriveProtectionUnitItemRequestBuilderGetQueryParameters.php +++ b/src/Generated/Solutions/BackupRestore/OneDriveForBusinessProtectionPolicies/Item/DriveProtectionUnits/Item/DriveProtectionUnitItemRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Contains the protection units associated with a OneDrive for Business protection policy. + * Contains the protection units associated with a OneDrive for Work or School protection policy. */ class DriveProtectionUnitItemRequestBuilderGetQueryParameters { diff --git a/src/Generated/Solutions/BackupRestore/OneDriveForBusinessRestoreSessions/Item/DriveRestoreArtifacts/Item/DriveRestoreArtifactItemRequestBuilder.php b/src/Generated/Solutions/BackupRestore/OneDriveForBusinessRestoreSessions/Item/DriveRestoreArtifacts/Item/DriveRestoreArtifactItemRequestBuilder.php index 1d93e7254af..f713f992992 100644 --- a/src/Generated/Solutions/BackupRestore/OneDriveForBusinessRestoreSessions/Item/DriveRestoreArtifacts/Item/DriveRestoreArtifactItemRequestBuilder.php +++ b/src/Generated/Solutions/BackupRestore/OneDriveForBusinessRestoreSessions/Item/DriveRestoreArtifacts/Item/DriveRestoreArtifactItemRequestBuilder.php @@ -53,7 +53,7 @@ public function delete(?DriveRestoreArtifactItemRequestBuilderDeleteRequestConfi } /** - * A collection of restore points and destination details that can be used to restore a OneDrive for Business drive. + * A collection of restore points and destination details that can be used to restore a OneDrive for Work or School drive. * @param DriveRestoreArtifactItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -100,7 +100,7 @@ public function toDeleteRequestInformation(?DriveRestoreArtifactItemRequestBuild } /** - * A collection of restore points and destination details that can be used to restore a OneDrive for Business drive. + * A collection of restore points and destination details that can be used to restore a OneDrive for Work or School drive. * @param DriveRestoreArtifactItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Solutions/BackupRestore/OneDriveForBusinessRestoreSessions/Item/DriveRestoreArtifacts/Item/DriveRestoreArtifactItemRequestBuilderGetQueryParameters.php b/src/Generated/Solutions/BackupRestore/OneDriveForBusinessRestoreSessions/Item/DriveRestoreArtifacts/Item/DriveRestoreArtifactItemRequestBuilderGetQueryParameters.php index d5fede0cd1f..c3f08a3adbb 100644 --- a/src/Generated/Solutions/BackupRestore/OneDriveForBusinessRestoreSessions/Item/DriveRestoreArtifacts/Item/DriveRestoreArtifactItemRequestBuilderGetQueryParameters.php +++ b/src/Generated/Solutions/BackupRestore/OneDriveForBusinessRestoreSessions/Item/DriveRestoreArtifacts/Item/DriveRestoreArtifactItemRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * A collection of restore points and destination details that can be used to restore a OneDrive for Business drive. + * A collection of restore points and destination details that can be used to restore a OneDrive for Work or School drive. */ class DriveRestoreArtifactItemRequestBuilderGetQueryParameters { diff --git a/src/Generated/Teams/Item/Channels/Item/Messages/MessagesRequestBuilder.php b/src/Generated/Teams/Item/Channels/Item/Messages/MessagesRequestBuilder.php index fc81c3ff570..955d697ee44 100644 --- a/src/Generated/Teams/Item/Channels/Item/Messages/MessagesRequestBuilder.php +++ b/src/Generated/Teams/Item/Channels/Item/Messages/MessagesRequestBuilder.php @@ -75,12 +75,12 @@ public function get(?MessagesRequestBuilderGetRequestConfiguration $requestConfi } /** - * Send a new chatMessage in the specified channel. + * Send a new chatMessage in the specified channel or a chat. * @param ChatMessage $body The request body * @param MessagesRequestBuilderPostRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception - * @link https://learn.microsoft.com/graph/api/channel-post-messages?view=graph-rest-beta Find more info here + * @link https://learn.microsoft.com/graph/api/chatmessage-post?view=graph-rest-beta Find more info here */ public function post(ChatMessage $body, ?MessagesRequestBuilderPostRequestConfiguration $requestConfiguration = null): Promise { $requestInfo = $this->toPostRequestInformation($body, $requestConfiguration); @@ -112,7 +112,7 @@ public function toGetRequestInformation(?MessagesRequestBuilderGetRequestConfigu } /** - * Send a new chatMessage in the specified channel. + * Send a new chatMessage in the specified channel or a chat. * @param ChatMessage $body The request body * @param MessagesRequestBuilderPostRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation diff --git a/src/Generated/Teams/Item/Schedule/OpenShifts/OpenShiftsRequestBuilder.php b/src/Generated/Teams/Item/Schedule/OpenShifts/OpenShiftsRequestBuilder.php index 9687d8cd584..f73e09a2061 100644 --- a/src/Generated/Teams/Item/Schedule/OpenShifts/OpenShiftsRequestBuilder.php +++ b/src/Generated/Teams/Item/Schedule/OpenShifts/OpenShiftsRequestBuilder.php @@ -67,7 +67,7 @@ public function get(?OpenShiftsRequestBuilderGetRequestConfiguration $requestCon } /** - * Create an instance of an openshift object. + * Create an instance of an openShift object. * @param OpenShift $body The request body * @param OpenShiftsRequestBuilderPostRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise @@ -104,7 +104,7 @@ public function toGetRequestInformation(?OpenShiftsRequestBuilderGetRequestConfi } /** - * Create an instance of an openshift object. + * Create an instance of an openShift object. * @param OpenShift $body The request body * @param OpenShiftsRequestBuilderPostRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation diff --git a/src/Generated/TenantRelationships/ManagedTenants/ManagementActions/Item/MicrosoftGraphManagedTenantsApply/MicrosoftGraphManagedTenantsApplyRequestBuilder.php b/src/Generated/TenantRelationships/ManagedTenants/ManagementActions/Item/MicrosoftGraphManagedTenantsApply/MicrosoftGraphManagedTenantsApplyRequestBuilder.php index 4fb66f3d3af..6d9137afb4c 100644 --- a/src/Generated/TenantRelationships/ManagedTenants/ManagementActions/Item/MicrosoftGraphManagedTenantsApply/MicrosoftGraphManagedTenantsApplyRequestBuilder.php +++ b/src/Generated/TenantRelationships/ManagedTenants/ManagementActions/Item/MicrosoftGraphManagedTenantsApply/MicrosoftGraphManagedTenantsApplyRequestBuilder.php @@ -31,7 +31,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Applies a management action against a specific managed tenant. By performing this operation the appropriate configurations will be made and policies created. As example when applying the require multifactor authentication for admins management action creates a Microsoft Entra Conditional Access policy that requires multifactor authentication for all users that have been assigned an administrative directory role. + * Applies a management action against a specific managed tenant. Performing this operation makes the appropriate configurations and creates the appropriate policies. For example, when applying the required multifactor authentication for admins, management action creates a Microsoft Entra Conditional Access policy that requires multifactor authentication for all users that are assigned an administrative directory role. * @param ApplyPostRequestBody $body The request body * @param MicrosoftGraphManagedTenantsApplyRequestBuilderPostRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise @@ -47,7 +47,7 @@ public function post(ApplyPostRequestBody $body, ?MicrosoftGraphManagedTenantsAp } /** - * Applies a management action against a specific managed tenant. By performing this operation the appropriate configurations will be made and policies created. As example when applying the require multifactor authentication for admins management action creates a Microsoft Entra Conditional Access policy that requires multifactor authentication for all users that have been assigned an administrative directory role. + * Applies a management action against a specific managed tenant. Performing this operation makes the appropriate configurations and creates the appropriate policies. For example, when applying the required multifactor authentication for admins, management action creates a Microsoft Entra Conditional Access policy that requires multifactor authentication for all users that are assigned an administrative directory role. * @param ApplyPostRequestBody $body The request body * @param MicrosoftGraphManagedTenantsApplyRequestBuilderPostRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation diff --git a/src/Generated/TenantRelationships/MultiTenantOrganization/JoinRequest/JoinRequestRequestBuilder.php b/src/Generated/TenantRelationships/MultiTenantOrganization/JoinRequest/JoinRequestRequestBuilder.php index b8fadcc41ca..11ebae85f1e 100644 --- a/src/Generated/TenantRelationships/MultiTenantOrganization/JoinRequest/JoinRequestRequestBuilder.php +++ b/src/Generated/TenantRelationships/MultiTenantOrganization/JoinRequest/JoinRequestRequestBuilder.php @@ -46,7 +46,7 @@ public function get(?JoinRequestRequestBuilderGetRequestConfiguration $requestCo } /** - * Join a multi-tenant organization, after the owner of the multi-tenant organization has added your tenant to the multi-tenant organization as pending. Before a tenant added to a multi-tenant organization can participate in the multi-tenant organization, the administrator of the joining tenant must submit a join request. To allow for asynchronous processing, you must wait a minimum of 2 hours between creation and joining a multi-tenant organization. Furthermore, to allow for asynchronous processing, you must wait up to 4 hours before joining a multi-tenant organization is completed. + * Join a multi-tenant organization, after the owner of the multi-tenant organization adds your tenant to the multi-tenant organization as pending. Before a tenant added to a multi-tenant organization can participate in the multi-tenant organization, the administrator of the joining tenant must submit a join request. To allow for asynchronous processing, you must wait a minimum of 2 hours between creation and joining a multi-tenant organization. Furthermore, to allow for asynchronous processing, you must wait up to 4 hours before joining a multi-tenant organization is completed. * @param MultiTenantOrganizationJoinRequestRecord $body The request body * @param JoinRequestRequestBuilderPatchRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise @@ -83,7 +83,7 @@ public function toGetRequestInformation(?JoinRequestRequestBuilderGetRequestConf } /** - * Join a multi-tenant organization, after the owner of the multi-tenant organization has added your tenant to the multi-tenant organization as pending. Before a tenant added to a multi-tenant organization can participate in the multi-tenant organization, the administrator of the joining tenant must submit a join request. To allow for asynchronous processing, you must wait a minimum of 2 hours between creation and joining a multi-tenant organization. Furthermore, to allow for asynchronous processing, you must wait up to 4 hours before joining a multi-tenant organization is completed. + * Join a multi-tenant organization, after the owner of the multi-tenant organization adds your tenant to the multi-tenant organization as pending. Before a tenant added to a multi-tenant organization can participate in the multi-tenant organization, the administrator of the joining tenant must submit a join request. To allow for asynchronous processing, you must wait a minimum of 2 hours between creation and joining a multi-tenant organization. Furthermore, to allow for asynchronous processing, you must wait up to 4 hours before joining a multi-tenant organization is completed. * @param MultiTenantOrganizationJoinRequestRecord $body The request body * @param JoinRequestRequestBuilderPatchRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation diff --git a/src/Generated/TenantRelationships/MultiTenantOrganization/MultiTenantOrganizationRequestBuilder.php b/src/Generated/TenantRelationships/MultiTenantOrganization/MultiTenantOrganizationRequestBuilder.php index 80ee643e6d8..d6511aba83e 100644 --- a/src/Generated/TenantRelationships/MultiTenantOrganization/MultiTenantOrganizationRequestBuilder.php +++ b/src/Generated/TenantRelationships/MultiTenantOrganization/MultiTenantOrganizationRequestBuilder.php @@ -62,12 +62,12 @@ public function get(?MultiTenantOrganizationRequestBuilderGetRequestConfiguratio } /** - * Update the properties of a multi-tenant organization. + * Create a new multi-tenant organization. By default, the creator tenant becomes an owner tenant upon successful creation. Only owner tenants can manage a multi-tenant organization. To allow for asynchronous processing, you must wait a minimum of 2 hours between creation and joining a multi-tenant organization. * @param MultiTenantOrganization $body The request body * @param MultiTenantOrganizationRequestBuilderPatchRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception - * @link https://learn.microsoft.com/graph/api/multitenantorganization-update?view=graph-rest-beta Find more info here + * @link https://learn.microsoft.com/graph/api/tenantrelationship-put-multitenantorganization?view=graph-rest-beta Find more info here */ public function patch(MultiTenantOrganization $body, ?MultiTenantOrganizationRequestBuilderPatchRequestConfiguration $requestConfiguration = null): Promise { $requestInfo = $this->toPatchRequestInformation($body, $requestConfiguration); @@ -99,7 +99,7 @@ public function toGetRequestInformation(?MultiTenantOrganizationRequestBuilderGe } /** - * Update the properties of a multi-tenant organization. + * Create a new multi-tenant organization. By default, the creator tenant becomes an owner tenant upon successful creation. Only owner tenants can manage a multi-tenant organization. To allow for asynchronous processing, you must wait a minimum of 2 hours between creation and joining a multi-tenant organization. * @param MultiTenantOrganization $body The request body * @param MultiTenantOrganizationRequestBuilderPatchRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation diff --git a/src/Generated/Users/Item/Authentication/HardwareOathMethods/AssignAndActivate/AssignAndActivateRequestBuilder.php b/src/Generated/Users/Item/Authentication/HardwareOathMethods/AssignAndActivate/AssignAndActivateRequestBuilder.php index 0383436aa5f..e279d04c96a 100644 --- a/src/Generated/Users/Item/Authentication/HardwareOathMethods/AssignAndActivate/AssignAndActivateRequestBuilder.php +++ b/src/Generated/Users/Item/Authentication/HardwareOathMethods/AssignAndActivate/AssignAndActivateRequestBuilder.php @@ -30,11 +30,12 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Invoke action assignAndActivate + * Assign and activate a hardware token at the same time. This operation requires the device ID to activate it. * @param AssignAndActivatePostRequestBody $body The request body * @param AssignAndActivateRequestBuilderPostRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception + * @link https://learn.microsoft.com/graph/api/hardwareoathauthenticationmethod-assignandactivate?view=graph-rest-beta Find more info here */ public function post(AssignAndActivatePostRequestBody $body, ?AssignAndActivateRequestBuilderPostRequestConfiguration $requestConfiguration = null): Promise { $requestInfo = $this->toPostRequestInformation($body, $requestConfiguration); @@ -45,7 +46,7 @@ public function post(AssignAndActivatePostRequestBody $body, ?AssignAndActivateR } /** - * Invoke action assignAndActivate + * Assign and activate a hardware token at the same time. This operation requires the device ID to activate it. * @param AssignAndActivatePostRequestBody $body The request body * @param AssignAndActivateRequestBuilderPostRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation diff --git a/src/Generated/Users/Item/Authentication/HardwareOathMethods/AssignAndActivateBySerialNumber/AssignAndActivateBySerialNumberRequestBuilder.php b/src/Generated/Users/Item/Authentication/HardwareOathMethods/AssignAndActivateBySerialNumber/AssignAndActivateBySerialNumberRequestBuilder.php index 83876337c58..226c5ba5c2f 100644 --- a/src/Generated/Users/Item/Authentication/HardwareOathMethods/AssignAndActivateBySerialNumber/AssignAndActivateBySerialNumberRequestBuilder.php +++ b/src/Generated/Users/Item/Authentication/HardwareOathMethods/AssignAndActivateBySerialNumber/AssignAndActivateBySerialNumberRequestBuilder.php @@ -30,11 +30,12 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Invoke action assignAndActivateBySerialNumber + * Assign and activate a hardware token at the same time by hardware token serial number. * @param AssignAndActivateBySerialNumberPostRequestBody $body The request body * @param AssignAndActivateBySerialNumberRequestBuilderPostRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception + * @link https://learn.microsoft.com/graph/api/hardwareoathauthenticationmethod-assignandactivatebyserialnumber?view=graph-rest-beta Find more info here */ public function post(AssignAndActivateBySerialNumberPostRequestBody $body, ?AssignAndActivateBySerialNumberRequestBuilderPostRequestConfiguration $requestConfiguration = null): Promise { $requestInfo = $this->toPostRequestInformation($body, $requestConfiguration); @@ -45,7 +46,7 @@ public function post(AssignAndActivateBySerialNumberPostRequestBody $body, ?Assi } /** - * Invoke action assignAndActivateBySerialNumber + * Assign and activate a hardware token at the same time by hardware token serial number. * @param AssignAndActivateBySerialNumberPostRequestBody $body The request body * @param AssignAndActivateBySerialNumberRequestBuilderPostRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation diff --git a/src/Generated/Users/Item/Authentication/HardwareOathMethods/HardwareOathMethodsRequestBuilder.php b/src/Generated/Users/Item/Authentication/HardwareOathMethods/HardwareOathMethodsRequestBuilder.php index 7c1acc96c91..b0005efacd1 100644 --- a/src/Generated/Users/Item/Authentication/HardwareOathMethods/HardwareOathMethodsRequestBuilder.php +++ b/src/Generated/Users/Item/Authentication/HardwareOathMethods/HardwareOathMethodsRequestBuilder.php @@ -68,7 +68,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get hardwareOathMethods from users + * The hardware OATH time-based one-time password (TOTP) devices assigned to a user for authentication. * @param HardwareOathMethodsRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -97,7 +97,7 @@ public function post(HardwareOathAuthenticationMethod $body, ?HardwareOathMethod } /** - * Get hardwareOathMethods from users + * The hardware OATH time-based one-time password (TOTP) devices assigned to a user for authentication. * @param HardwareOathMethodsRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/Authentication/HardwareOathMethods/HardwareOathMethodsRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/Authentication/HardwareOathMethods/HardwareOathMethodsRequestBuilderGetQueryParameters.php index 03b8386e46f..4ea33746fa4 100644 --- a/src/Generated/Users/Item/Authentication/HardwareOathMethods/HardwareOathMethodsRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/Authentication/HardwareOathMethods/HardwareOathMethodsRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get hardwareOathMethods from users + * The hardware OATH time-based one-time password (TOTP) devices assigned to a user for authentication. */ class HardwareOathMethodsRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/Activate/ActivateRequestBuilder.php b/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/Activate/ActivateRequestBuilder.php index 89d7047f8fd..de65918edd2 100644 --- a/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/Activate/ActivateRequestBuilder.php +++ b/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/Activate/ActivateRequestBuilder.php @@ -30,11 +30,12 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Invoke action activate + * Activate a hardware OATH token that is already assigned to a user. A user can self-activate their token or an admin can activate for a user. * @param ActivatePostRequestBody $body The request body * @param ActivateRequestBuilderPostRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception + * @link https://learn.microsoft.com/graph/api/hardwareoathauthenticationmethod-activate?view=graph-rest-beta Find more info here */ public function post(ActivatePostRequestBody $body, ?ActivateRequestBuilderPostRequestConfiguration $requestConfiguration = null): Promise { $requestInfo = $this->toPostRequestInformation($body, $requestConfiguration); @@ -45,7 +46,7 @@ public function post(ActivatePostRequestBody $body, ?ActivateRequestBuilderPostR } /** - * Invoke action activate + * Activate a hardware OATH token that is already assigned to a user. A user can self-activate their token or an admin can activate for a user. * @param ActivatePostRequestBody $body The request body * @param ActivateRequestBuilderPostRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation diff --git a/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/Deactivate/DeactivateRequestBuilder.php b/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/Deactivate/DeactivateRequestBuilder.php index 247d0339a98..6b6895f280e 100644 --- a/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/Deactivate/DeactivateRequestBuilder.php +++ b/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/Deactivate/DeactivateRequestBuilder.php @@ -30,10 +30,11 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Invoke action deactivate + * Deactive a hardware OATH token. It remains assigned to a user. * @param DeactivateRequestBuilderPostRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception + * @link https://learn.microsoft.com/graph/api/hardwareoathauthenticationmethod-deactivate?view=graph-rest-beta Find more info here */ public function post(?DeactivateRequestBuilderPostRequestConfiguration $requestConfiguration = null): Promise { $requestInfo = $this->toPostRequestInformation($requestConfiguration); @@ -44,7 +45,7 @@ public function post(?DeactivateRequestBuilderPostRequestConfiguration $requestC } /** - * Invoke action deactivate + * Deactive a hardware OATH token. It remains assigned to a user. * @param DeactivateRequestBuilderPostRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/Device/AssignTo/AssignToRequestBuilder.php b/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/Device/AssignTo/AssignToRequestBuilder.php index bc9749593c2..0ebc3124652 100644 --- a/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/Device/AssignTo/AssignToRequestBuilder.php +++ b/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/Device/AssignTo/AssignToRequestBuilder.php @@ -47,7 +47,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get assignTo from users + * Assign the hardware OATH token to a user. * @param AssignToRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -61,7 +61,7 @@ public function get(?AssignToRequestBuilderGetRequestConfiguration $requestConfi } /** - * Get assignTo from users + * Assign the hardware OATH token to a user. * @param AssignToRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/Device/AssignTo/AssignToRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/Device/AssignTo/AssignToRequestBuilderGetQueryParameters.php index 69677c1ebae..0e71800087d 100644 --- a/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/Device/AssignTo/AssignToRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/Device/AssignTo/AssignToRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get assignTo from users + * Assign the hardware OATH token to a user. */ class AssignToRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/Device/DeviceRequestBuilder.php b/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/Device/DeviceRequestBuilder.php index e92a0ba4f7c..935fb2b1571 100644 --- a/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/Device/DeviceRequestBuilder.php +++ b/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/Device/DeviceRequestBuilder.php @@ -61,7 +61,7 @@ public function delete(?DeviceRequestBuilderDeleteRequestConfiguration $requestC } /** - * Get device from users + * Exposes the hardware OATH method in the directory. * @param DeviceRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -108,7 +108,7 @@ public function toDeleteRequestInformation(?DeviceRequestBuilderDeleteRequestCon } /** - * Get device from users + * Exposes the hardware OATH method in the directory. * @param DeviceRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/Device/DeviceRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/Device/DeviceRequestBuilderGetQueryParameters.php index a6e72ffefa4..c8abc75b473 100644 --- a/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/Device/DeviceRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/Device/DeviceRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get device from users + * Exposes the hardware OATH method in the directory. */ class DeviceRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/Device/HardwareOathDevices/HardwareOathDevicesRequestBuilder.php b/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/Device/HardwareOathDevices/HardwareOathDevicesRequestBuilder.php index 979cace90c1..1b1013b1f0c 100644 --- a/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/Device/HardwareOathDevices/HardwareOathDevicesRequestBuilder.php +++ b/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/Device/HardwareOathDevices/HardwareOathDevicesRequestBuilder.php @@ -52,7 +52,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get hardwareOathDevices from users + * Exposes the hardware OATH method in the directory. * @param HardwareOathDevicesRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -81,7 +81,7 @@ public function post(HardwareOathTokenAuthenticationMethodDevice $body, ?Hardwar } /** - * Get hardwareOathDevices from users + * Exposes the hardware OATH method in the directory. * @param HardwareOathDevicesRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/Device/HardwareOathDevices/HardwareOathDevicesRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/Device/HardwareOathDevices/HardwareOathDevicesRequestBuilderGetQueryParameters.php index 02a0d702e28..6f7829e6e21 100644 --- a/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/Device/HardwareOathDevices/HardwareOathDevicesRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/Device/HardwareOathDevices/HardwareOathDevicesRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get hardwareOathDevices from users + * Exposes the hardware OATH method in the directory. */ class HardwareOathDevicesRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/Device/HardwareOathDevices/Item/AssignTo/AssignToRequestBuilder.php b/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/Device/HardwareOathDevices/Item/AssignTo/AssignToRequestBuilder.php index 3da3bb2b1e9..b07eb3e6a2d 100644 --- a/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/Device/HardwareOathDevices/Item/AssignTo/AssignToRequestBuilder.php +++ b/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/Device/HardwareOathDevices/Item/AssignTo/AssignToRequestBuilder.php @@ -47,7 +47,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get assignTo from users + * Assign the hardware OATH token to a user. * @param AssignToRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -61,7 +61,7 @@ public function get(?AssignToRequestBuilderGetRequestConfiguration $requestConfi } /** - * Get assignTo from users + * Assign the hardware OATH token to a user. * @param AssignToRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/Device/HardwareOathDevices/Item/AssignTo/AssignToRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/Device/HardwareOathDevices/Item/AssignTo/AssignToRequestBuilderGetQueryParameters.php index 17aae8347b6..1639f0e760d 100644 --- a/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/Device/HardwareOathDevices/Item/AssignTo/AssignToRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/Device/HardwareOathDevices/Item/AssignTo/AssignToRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get assignTo from users + * Assign the hardware OATH token to a user. */ class AssignToRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/Device/HardwareOathDevices/Item/HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilder.php b/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/Device/HardwareOathDevices/Item/HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilder.php index 9a417fbac7e..a9bf0b556f5 100644 --- a/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/Device/HardwareOathDevices/Item/HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilder.php +++ b/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/Device/HardwareOathDevices/Item/HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilder.php @@ -53,7 +53,7 @@ public function delete(?HardwareOathTokenAuthenticationMethodDeviceItemRequestBu } /** - * Get hardwareOathDevices from users + * Exposes the hardware OATH method in the directory. * @param HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -100,7 +100,7 @@ public function toDeleteRequestInformation(?HardwareOathTokenAuthenticationMetho } /** - * Get hardwareOathDevices from users + * Exposes the hardware OATH method in the directory. * @param HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/Device/HardwareOathDevices/Item/HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/Device/HardwareOathDevices/Item/HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilderGetQueryParameters.php index 3fbc9487bc8..93c5be01c1f 100644 --- a/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/Device/HardwareOathDevices/Item/HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/Device/HardwareOathDevices/Item/HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get hardwareOathDevices from users + * Exposes the hardware OATH method in the directory. */ class HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/HardwareOathAuthenticationMethodItemRequestBuilder.php b/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/HardwareOathAuthenticationMethodItemRequestBuilder.php index 717fc2471d6..419738b9bce 100644 --- a/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/HardwareOathAuthenticationMethodItemRequestBuilder.php +++ b/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/HardwareOathAuthenticationMethodItemRequestBuilder.php @@ -69,7 +69,7 @@ public function delete(?HardwareOathAuthenticationMethodItemRequestBuilderDelete } /** - * Get hardwareOathMethods from users + * The hardware OATH time-based one-time password (TOTP) devices assigned to a user for authentication. * @param HardwareOathAuthenticationMethodItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -101,7 +101,7 @@ public function toDeleteRequestInformation(?HardwareOathAuthenticationMethodItem } /** - * Get hardwareOathMethods from users + * The hardware OATH time-based one-time password (TOTP) devices assigned to a user for authentication. * @param HardwareOathAuthenticationMethodItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/HardwareOathAuthenticationMethodItemRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/HardwareOathAuthenticationMethodItemRequestBuilderGetQueryParameters.php index e47df35f7f5..6f4e66e30f3 100644 --- a/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/HardwareOathAuthenticationMethodItemRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/Authentication/HardwareOathMethods/Item/HardwareOathAuthenticationMethodItemRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get hardwareOathMethods from users + * The hardware OATH time-based one-time password (TOTP) devices assigned to a user for authentication. */ class HardwareOathAuthenticationMethodItemRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/Calendar/CalendarView/Delta/DeltaRequestBuilder.php b/src/Generated/Users/Item/Calendar/CalendarView/Delta/DeltaRequestBuilder.php index 24926d10f15..adbaf9dabc2 100644 --- a/src/Generated/Users/Item/Calendar/CalendarView/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Users/Item/Calendar/CalendarView/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/Calendar/CalendarView/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/Calendar/CalendarView/Delta/DeltaRequestBuilderGetQueryParameters.php index faf44247871..30bf7324af4 100644 --- a/src/Generated/Users/Item/Calendar/CalendarView/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/Calendar/CalendarView/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/Calendar/CalendarView/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php b/src/Generated/Users/Item/Calendar/CalendarView/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php index 7b3f43ae317..db3f411dbd5 100644 --- a/src/Generated/Users/Item/Calendar/CalendarView/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Users/Item/Calendar/CalendarView/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/Calendar/CalendarView/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/Calendar/CalendarView/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php index e7b35b35ddd..b927539ab09 100644 --- a/src/Generated/Users/Item/Calendar/CalendarView/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/Calendar/CalendarView/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/Calendar/CalendarView/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilder.php b/src/Generated/Users/Item/Calendar/CalendarView/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilder.php index 4d4a4ed3b0a..7673772815b 100644 --- a/src/Generated/Users/Item/Calendar/CalendarView/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Users/Item/Calendar/CalendarView/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/Calendar/CalendarView/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/Calendar/CalendarView/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php index 645433b4e34..910533c6dc1 100644 --- a/src/Generated/Users/Item/Calendar/CalendarView/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/Calendar/CalendarView/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/Calendar/CalendarView/Item/Instances/Delta/DeltaRequestBuilder.php b/src/Generated/Users/Item/Calendar/CalendarView/Item/Instances/Delta/DeltaRequestBuilder.php index 299fa5a1243..cd4a6206aa2 100644 --- a/src/Generated/Users/Item/Calendar/CalendarView/Item/Instances/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Users/Item/Calendar/CalendarView/Item/Instances/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/Calendar/CalendarView/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/Calendar/CalendarView/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php index d4ac57aa83f..6dada2a164c 100644 --- a/src/Generated/Users/Item/Calendar/CalendarView/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/Calendar/CalendarView/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/Calendar/CalendarView/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php b/src/Generated/Users/Item/Calendar/CalendarView/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php index 479ef445bf1..acf9b8a0262 100644 --- a/src/Generated/Users/Item/Calendar/CalendarView/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Users/Item/Calendar/CalendarView/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/Calendar/CalendarView/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/Calendar/CalendarView/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php index efbbbe76192..bba1b168e35 100644 --- a/src/Generated/Users/Item/Calendar/CalendarView/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/Calendar/CalendarView/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/Calendar/Events/Delta/DeltaRequestBuilder.php b/src/Generated/Users/Item/Calendar/Events/Delta/DeltaRequestBuilder.php index b5815a28897..0131229294e 100644 --- a/src/Generated/Users/Item/Calendar/Events/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Users/Item/Calendar/Events/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/Calendar/Events/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/Calendar/Events/Delta/DeltaRequestBuilderGetQueryParameters.php index 9e8dfbfc7f7..378896cf620 100644 --- a/src/Generated/Users/Item/Calendar/Events/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/Calendar/Events/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/Calendar/Events/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php b/src/Generated/Users/Item/Calendar/Events/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php index bfd11407651..a842dda39a7 100644 --- a/src/Generated/Users/Item/Calendar/Events/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Users/Item/Calendar/Events/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/Calendar/Events/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/Calendar/Events/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php index 57c4c0e6be5..071b06ed886 100644 --- a/src/Generated/Users/Item/Calendar/Events/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/Calendar/Events/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/Calendar/Events/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilder.php b/src/Generated/Users/Item/Calendar/Events/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilder.php index 2e6360e7ef7..5d3b0ae62f3 100644 --- a/src/Generated/Users/Item/Calendar/Events/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Users/Item/Calendar/Events/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/Calendar/Events/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/Calendar/Events/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php index 9d3df8a1ec4..b78b08abd53 100644 --- a/src/Generated/Users/Item/Calendar/Events/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/Calendar/Events/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/Calendar/Events/Item/Instances/Delta/DeltaRequestBuilder.php b/src/Generated/Users/Item/Calendar/Events/Item/Instances/Delta/DeltaRequestBuilder.php index 61feb9e4882..7492d2995a7 100644 --- a/src/Generated/Users/Item/Calendar/Events/Item/Instances/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Users/Item/Calendar/Events/Item/Instances/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/Calendar/Events/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/Calendar/Events/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php index decf322de78..70dc8f04531 100644 --- a/src/Generated/Users/Item/Calendar/Events/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/Calendar/Events/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/Calendar/Events/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php b/src/Generated/Users/Item/Calendar/Events/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php index ffce6c78212..07a58ebf1ab 100644 --- a/src/Generated/Users/Item/Calendar/Events/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Users/Item/Calendar/Events/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/Calendar/Events/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/Calendar/Events/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php index 7311a0e30de..934eda22567 100644 --- a/src/Generated/Users/Item/Calendar/Events/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/Calendar/Events/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/CalendarView/Delta/DeltaRequestBuilder.php b/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/CalendarView/Delta/DeltaRequestBuilder.php index 13dad0ac8a2..beb2d84958f 100644 --- a/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/CalendarView/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/CalendarView/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/CalendarView/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/CalendarView/Delta/DeltaRequestBuilderGetQueryParameters.php index b05ead70327..25c376e91e2 100644 --- a/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/CalendarView/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/CalendarView/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/CalendarView/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php b/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/CalendarView/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php index 9ad969499e3..3026dbed83e 100644 --- a/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/CalendarView/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/CalendarView/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/CalendarView/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/CalendarView/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php index 473319f4ed3..9e9e0155335 100644 --- a/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/CalendarView/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/CalendarView/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/CalendarView/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilder.php b/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/CalendarView/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilder.php index 4a06259c8f2..9598f305947 100644 --- a/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/CalendarView/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/CalendarView/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/CalendarView/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/CalendarView/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php index b1af003e8af..ed5f0f79479 100644 --- a/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/CalendarView/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/CalendarView/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/CalendarView/Item/Instances/Delta/DeltaRequestBuilder.php b/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/CalendarView/Item/Instances/Delta/DeltaRequestBuilder.php index 56b7cf92937..90f61a4caca 100644 --- a/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/CalendarView/Item/Instances/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/CalendarView/Item/Instances/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/CalendarView/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/CalendarView/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php index aaf205f47ed..fb3247ba087 100644 --- a/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/CalendarView/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/CalendarView/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/CalendarView/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php b/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/CalendarView/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php index 41bf2cf681e..5cc87259cf4 100644 --- a/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/CalendarView/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/CalendarView/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/CalendarView/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/CalendarView/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php index 77bc303d9b1..6bb384a9f8a 100644 --- a/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/CalendarView/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/CalendarView/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/Events/Delta/DeltaRequestBuilder.php b/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/Events/Delta/DeltaRequestBuilder.php index 9ce5acda0d8..0fe812b4a28 100644 --- a/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/Events/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/Events/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/Events/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/Events/Delta/DeltaRequestBuilderGetQueryParameters.php index 00201d60029..8491e75f7bc 100644 --- a/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/Events/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/Events/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/Events/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php b/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/Events/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php index 0de2886f388..a11ab84e490 100644 --- a/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/Events/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/Events/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/Events/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/Events/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php index 1e26f234426..6dac57f7e36 100644 --- a/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/Events/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/Events/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/Events/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilder.php b/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/Events/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilder.php index 3e58b95343d..58f46b7bac9 100644 --- a/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/Events/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/Events/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/Events/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/Events/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php index fbb0d2322b4..86b58f7b902 100644 --- a/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/Events/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/Events/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/Events/Item/Instances/Delta/DeltaRequestBuilder.php b/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/Events/Item/Instances/Delta/DeltaRequestBuilder.php index 9235de9cfd7..b6258cdde5f 100644 --- a/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/Events/Item/Instances/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/Events/Item/Instances/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/Events/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/Events/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php index 4f3664d1822..651147f9bfd 100644 --- a/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/Events/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/Events/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/Events/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php b/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/Events/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php index 473ec20fa63..67f219eb8f7 100644 --- a/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/Events/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/Events/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/Events/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/Events/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php index 21eb571cff5..e10ffe69eee 100644 --- a/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/Events/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/CalendarGroups/Item/Calendars/Item/Events/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/CalendarView/Delta/DeltaRequestBuilder.php b/src/Generated/Users/Item/CalendarView/Delta/DeltaRequestBuilder.php index 181397c5fd2..a8f538a1541 100644 --- a/src/Generated/Users/Item/CalendarView/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Users/Item/CalendarView/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/CalendarView/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/CalendarView/Delta/DeltaRequestBuilderGetQueryParameters.php index a5af821847c..dae44541feb 100644 --- a/src/Generated/Users/Item/CalendarView/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/CalendarView/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/CalendarView/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php b/src/Generated/Users/Item/CalendarView/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php index aa62f179d1c..9c407694dfb 100644 --- a/src/Generated/Users/Item/CalendarView/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Users/Item/CalendarView/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/CalendarView/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/CalendarView/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php index b77b3ba7bc6..a77b5abc0ae 100644 --- a/src/Generated/Users/Item/CalendarView/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/CalendarView/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/CalendarView/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilder.php b/src/Generated/Users/Item/CalendarView/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilder.php index aec4b3926ff..bfba1e1795f 100644 --- a/src/Generated/Users/Item/CalendarView/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Users/Item/CalendarView/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/CalendarView/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/CalendarView/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php index 1349a3f536f..ab004faacf4 100644 --- a/src/Generated/Users/Item/CalendarView/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/CalendarView/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/CalendarView/Item/Instances/Delta/DeltaRequestBuilder.php b/src/Generated/Users/Item/CalendarView/Item/Instances/Delta/DeltaRequestBuilder.php index 367dc68ec49..9662bc86ca6 100644 --- a/src/Generated/Users/Item/CalendarView/Item/Instances/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Users/Item/CalendarView/Item/Instances/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/CalendarView/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/CalendarView/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php index 5fcb8d82c0e..14536db80a4 100644 --- a/src/Generated/Users/Item/CalendarView/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/CalendarView/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/CalendarView/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php b/src/Generated/Users/Item/CalendarView/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php index 017cc7daf7f..a5e65ef382b 100644 --- a/src/Generated/Users/Item/CalendarView/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Users/Item/CalendarView/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/CalendarView/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/CalendarView/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php index bbb8e78fecb..cca466fa00b 100644 --- a/src/Generated/Users/Item/CalendarView/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/CalendarView/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/Calendars/Item/CalendarView/Delta/DeltaRequestBuilder.php b/src/Generated/Users/Item/Calendars/Item/CalendarView/Delta/DeltaRequestBuilder.php index f5e5ef2226b..14d880415f4 100644 --- a/src/Generated/Users/Item/Calendars/Item/CalendarView/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Users/Item/Calendars/Item/CalendarView/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/Calendars/Item/CalendarView/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/Calendars/Item/CalendarView/Delta/DeltaRequestBuilderGetQueryParameters.php index 43c4739d2ad..9298a7124c8 100644 --- a/src/Generated/Users/Item/Calendars/Item/CalendarView/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/Calendars/Item/CalendarView/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/Calendars/Item/CalendarView/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php b/src/Generated/Users/Item/Calendars/Item/CalendarView/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php index 7f9e315f1bc..12dee443c86 100644 --- a/src/Generated/Users/Item/Calendars/Item/CalendarView/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Users/Item/Calendars/Item/CalendarView/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/Calendars/Item/CalendarView/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/Calendars/Item/CalendarView/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php index dd3bb3f58e5..6c88a3395a1 100644 --- a/src/Generated/Users/Item/Calendars/Item/CalendarView/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/Calendars/Item/CalendarView/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/Calendars/Item/CalendarView/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilder.php b/src/Generated/Users/Item/Calendars/Item/CalendarView/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilder.php index f0580ce35fb..c61b94ed109 100644 --- a/src/Generated/Users/Item/Calendars/Item/CalendarView/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Users/Item/Calendars/Item/CalendarView/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/Calendars/Item/CalendarView/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/Calendars/Item/CalendarView/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php index 6e1d94e4c7f..5c2c1f88d7c 100644 --- a/src/Generated/Users/Item/Calendars/Item/CalendarView/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/Calendars/Item/CalendarView/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/Calendars/Item/CalendarView/Item/Instances/Delta/DeltaRequestBuilder.php b/src/Generated/Users/Item/Calendars/Item/CalendarView/Item/Instances/Delta/DeltaRequestBuilder.php index 4de77206908..44d6d3e1e16 100644 --- a/src/Generated/Users/Item/Calendars/Item/CalendarView/Item/Instances/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Users/Item/Calendars/Item/CalendarView/Item/Instances/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/Calendars/Item/CalendarView/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/Calendars/Item/CalendarView/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php index adcc7416f21..3e90f6762a7 100644 --- a/src/Generated/Users/Item/Calendars/Item/CalendarView/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/Calendars/Item/CalendarView/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/Calendars/Item/CalendarView/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php b/src/Generated/Users/Item/Calendars/Item/CalendarView/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php index e2f66c3394f..0451d9514e1 100644 --- a/src/Generated/Users/Item/Calendars/Item/CalendarView/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Users/Item/Calendars/Item/CalendarView/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/Calendars/Item/CalendarView/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/Calendars/Item/CalendarView/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php index 4778a35a709..fb350e69b32 100644 --- a/src/Generated/Users/Item/Calendars/Item/CalendarView/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/Calendars/Item/CalendarView/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/Calendars/Item/Events/Delta/DeltaRequestBuilder.php b/src/Generated/Users/Item/Calendars/Item/Events/Delta/DeltaRequestBuilder.php index 2f72fed4e27..117617fab95 100644 --- a/src/Generated/Users/Item/Calendars/Item/Events/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Users/Item/Calendars/Item/Events/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/Calendars/Item/Events/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/Calendars/Item/Events/Delta/DeltaRequestBuilderGetQueryParameters.php index e2f2442f0d1..888e67033e9 100644 --- a/src/Generated/Users/Item/Calendars/Item/Events/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/Calendars/Item/Events/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/Calendars/Item/Events/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php b/src/Generated/Users/Item/Calendars/Item/Events/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php index 8a5f2250353..a1a5c61858a 100644 --- a/src/Generated/Users/Item/Calendars/Item/Events/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Users/Item/Calendars/Item/Events/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/Calendars/Item/Events/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/Calendars/Item/Events/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php index ebccff2e1a1..da7def1532a 100644 --- a/src/Generated/Users/Item/Calendars/Item/Events/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/Calendars/Item/Events/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/Calendars/Item/Events/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilder.php b/src/Generated/Users/Item/Calendars/Item/Events/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilder.php index 2e811d97171..a00b90305c6 100644 --- a/src/Generated/Users/Item/Calendars/Item/Events/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Users/Item/Calendars/Item/Events/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/Calendars/Item/Events/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/Calendars/Item/Events/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php index 116946702e7..73d302f7350 100644 --- a/src/Generated/Users/Item/Calendars/Item/Events/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/Calendars/Item/Events/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/Calendars/Item/Events/Item/Instances/Delta/DeltaRequestBuilder.php b/src/Generated/Users/Item/Calendars/Item/Events/Item/Instances/Delta/DeltaRequestBuilder.php index d4c39455198..c97852ef26a 100644 --- a/src/Generated/Users/Item/Calendars/Item/Events/Item/Instances/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Users/Item/Calendars/Item/Events/Item/Instances/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/Calendars/Item/Events/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/Calendars/Item/Events/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php index 88af05927c9..189956c591c 100644 --- a/src/Generated/Users/Item/Calendars/Item/Events/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/Calendars/Item/Events/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/Calendars/Item/Events/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php b/src/Generated/Users/Item/Calendars/Item/Events/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php index c5ec69e1837..de519044fc2 100644 --- a/src/Generated/Users/Item/Calendars/Item/Events/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Users/Item/Calendars/Item/Events/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/Calendars/Item/Events/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/Calendars/Item/Events/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php index 6667d9465a6..ef8fff82fa1 100644 --- a/src/Generated/Users/Item/Calendars/Item/Events/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/Calendars/Item/Events/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/CloudPCs/Item/RetrieveReviewStatus/RetrieveReviewStatusRequestBuilder.php b/src/Generated/Users/Item/CloudPCs/Item/RetrieveReviewStatus/RetrieveReviewStatusRequestBuilder.php index e73135091b1..46f67038174 100644 --- a/src/Generated/Users/Item/CloudPCs/Item/RetrieveReviewStatus/RetrieveReviewStatusRequestBuilder.php +++ b/src/Generated/Users/Item/CloudPCs/Item/RetrieveReviewStatus/RetrieveReviewStatusRequestBuilder.php @@ -31,10 +31,11 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Invoke function retrieveReviewStatus + * Get the review status of a Cloud PC. * @param RetrieveReviewStatusRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception + * @link https://learn.microsoft.com/graph/api/cloudpc-retrievereviewstatus?view=graph-rest-beta Find more info here */ public function get(?RetrieveReviewStatusRequestBuilderGetRequestConfiguration $requestConfiguration = null): Promise { $requestInfo = $this->toGetRequestInformation($requestConfiguration); @@ -45,7 +46,7 @@ public function get(?RetrieveReviewStatusRequestBuilderGetRequestConfiguration $ } /** - * Invoke function retrieveReviewStatus + * Get the review status of a Cloud PC. * @param RetrieveReviewStatusRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/CloudPCs/Item/RetrieveSnapshots/RetrieveSnapshotsRequestBuilder.php b/src/Generated/Users/Item/CloudPCs/Item/RetrieveSnapshots/RetrieveSnapshotsRequestBuilder.php index f1cf3d4fb7b..a9d4dc61ea8 100644 --- a/src/Generated/Users/Item/CloudPCs/Item/RetrieveSnapshots/RetrieveSnapshotsRequestBuilder.php +++ b/src/Generated/Users/Item/CloudPCs/Item/RetrieveSnapshots/RetrieveSnapshotsRequestBuilder.php @@ -30,10 +30,11 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Invoke function retrieveSnapshots + * List all cloudPcSnapshot resources for a Cloud PC. * @param RetrieveSnapshotsRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception + * @link https://learn.microsoft.com/graph/api/cloudpc-retrievesnapshots?view=graph-rest-beta Find more info here */ public function get(?RetrieveSnapshotsRequestBuilderGetRequestConfiguration $requestConfiguration = null): Promise { $requestInfo = $this->toGetRequestInformation($requestConfiguration); @@ -44,7 +45,7 @@ public function get(?RetrieveSnapshotsRequestBuilderGetRequestConfiguration $req } /** - * Invoke function retrieveSnapshots + * List all cloudPcSnapshot resources for a Cloud PC. * @param RetrieveSnapshotsRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/CloudPCs/Item/RetrieveSnapshots/RetrieveSnapshotsRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/CloudPCs/Item/RetrieveSnapshots/RetrieveSnapshotsRequestBuilderGetQueryParameters.php index b713bc765a6..ec9fd83302e 100644 --- a/src/Generated/Users/Item/CloudPCs/Item/RetrieveSnapshots/RetrieveSnapshotsRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/CloudPCs/Item/RetrieveSnapshots/RetrieveSnapshotsRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Invoke function retrieveSnapshots + * List all cloudPcSnapshot resources for a Cloud PC. */ class RetrieveSnapshotsRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/CloudPCs/Item/SetReviewStatus/SetReviewStatusRequestBuilder.php b/src/Generated/Users/Item/CloudPCs/Item/SetReviewStatus/SetReviewStatusRequestBuilder.php index 472dc33562f..badc7154ced 100644 --- a/src/Generated/Users/Item/CloudPCs/Item/SetReviewStatus/SetReviewStatusRequestBuilder.php +++ b/src/Generated/Users/Item/CloudPCs/Item/SetReviewStatus/SetReviewStatusRequestBuilder.php @@ -30,11 +30,12 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Invoke action setReviewStatus + * Set the review status of a specific Cloud PC device using the Cloud PC ID. Use this API to set the review status of a Cloud PC to in review if you consider a Cloud PC suspicious. After the review is completed, use this API again to set the Cloud PC back to a normal state. * @param SetReviewStatusPostRequestBody $body The request body * @param SetReviewStatusRequestBuilderPostRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception + * @link https://learn.microsoft.com/graph/api/cloudpc-setreviewstatus?view=graph-rest-beta Find more info here */ public function post(SetReviewStatusPostRequestBody $body, ?SetReviewStatusRequestBuilderPostRequestConfiguration $requestConfiguration = null): Promise { $requestInfo = $this->toPostRequestInformation($body, $requestConfiguration); @@ -45,7 +46,7 @@ public function post(SetReviewStatusPostRequestBody $body, ?SetReviewStatusReque } /** - * Invoke action setReviewStatus + * Set the review status of a specific Cloud PC device using the Cloud PC ID. Use this API to set the review status of a Cloud PC to in review if you consider a Cloud PC suspicious. After the review is completed, use this API again to set the Cloud PC back to a normal state. * @param SetReviewStatusPostRequestBody $body The request body * @param SetReviewStatusRequestBuilderPostRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation diff --git a/src/Generated/Users/Item/Events/Delta/DeltaRequestBuilder.php b/src/Generated/Users/Item/Events/Delta/DeltaRequestBuilder.php index 735870c1574..86c75a17344 100644 --- a/src/Generated/Users/Item/Events/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Users/Item/Events/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/Events/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/Events/Delta/DeltaRequestBuilderGetQueryParameters.php index e1b08efc4d5..b63f61d7ba5 100644 --- a/src/Generated/Users/Item/Events/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/Events/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/Events/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php b/src/Generated/Users/Item/Events/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php index 9c037fb599c..3a57ccf80d9 100644 --- a/src/Generated/Users/Item/Events/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Users/Item/Events/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/Events/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/Events/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php index 4a77979fd54..f34f40fe255 100644 --- a/src/Generated/Users/Item/Events/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/Events/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/Events/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilder.php b/src/Generated/Users/Item/Events/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilder.php index 5ccf78e371c..e6b728509f0 100644 --- a/src/Generated/Users/Item/Events/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Users/Item/Events/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/Events/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/Events/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php index 1d887e8b1d5..764185cbefe 100644 --- a/src/Generated/Users/Item/Events/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/Events/Item/ExceptionOccurrences/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/Events/Item/Instances/Delta/DeltaRequestBuilder.php b/src/Generated/Users/Item/Events/Item/Instances/Delta/DeltaRequestBuilder.php index 6bd863273e8..2941e9c540a 100644 --- a/src/Generated/Users/Item/Events/Item/Instances/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Users/Item/Events/Item/Instances/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/Events/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/Events/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php index e5d7afa7622..ed3fc508ced 100644 --- a/src/Generated/Users/Item/Events/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/Events/Item/Instances/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/Events/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php b/src/Generated/Users/Item/Events/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php index 74288e0ebc0..91d22848422 100644 --- a/src/Generated/Users/Item/Events/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Users/Item/Events/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/Events/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/Events/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php index e2a5e317ef5..9996abc7bc7 100644 --- a/src/Generated/Users/Item/Events/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/Events/Item/Instances/Item/ExceptionOccurrences/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + * Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/MailFolders/Item/ChildFolders/Item/Messages/Delta/DeltaRequestBuilder.php b/src/Generated/Users/Item/MailFolders/Item/ChildFolders/Item/Messages/Delta/DeltaRequestBuilder.php index b2008629d83..be160036c02 100644 --- a/src/Generated/Users/Item/MailFolders/Item/ChildFolders/Item/Messages/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Users/Item/MailFolders/Item/ChildFolders/Item/Messages/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of messages that have been added, deleted, or updated in a specified folder. A delta function call for messages in a folder is similar to a GET request, except that by appropriatelyapplying state tokens in one or more of these calls, you can [query for incremental changes in the messages inthat folder](/graph/delta-query-messages). This allows you to maintain and synchronize a local store of a user's messages withouthaving to fetch the entire set of messages from the server every time. + * Get a set of messages that were added, deleted, or updated in a specified folder. A delta function call for messages in a folder is similar to a GET request, except that by appropriatelyapplying state tokens in one or more of these calls, you can [query for incremental changes in the messages inthat folder](/graph/delta-query-messages). Using deltas allows you toincrementally maintain and synchronize a local store of a user's messages. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of messages that have been added, deleted, or updated in a specified folder. A delta function call for messages in a folder is similar to a GET request, except that by appropriatelyapplying state tokens in one or more of these calls, you can [query for incremental changes in the messages inthat folder](/graph/delta-query-messages). This allows you to maintain and synchronize a local store of a user's messages withouthaving to fetch the entire set of messages from the server every time. + * Get a set of messages that were added, deleted, or updated in a specified folder. A delta function call for messages in a folder is similar to a GET request, except that by appropriatelyapplying state tokens in one or more of these calls, you can [query for incremental changes in the messages inthat folder](/graph/delta-query-messages). Using deltas allows you toincrementally maintain and synchronize a local store of a user's messages. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/MailFolders/Item/ChildFolders/Item/Messages/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/MailFolders/Item/ChildFolders/Item/Messages/Delta/DeltaRequestBuilderGetQueryParameters.php index 9394889fcae..003efeb7b46 100644 --- a/src/Generated/Users/Item/MailFolders/Item/ChildFolders/Item/Messages/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/MailFolders/Item/ChildFolders/Item/Messages/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of messages that have been added, deleted, or updated in a specified folder. A delta function call for messages in a folder is similar to a GET request, except that by appropriatelyapplying state tokens in one or more of these calls, you can [query for incremental changes in the messages inthat folder](/graph/delta-query-messages). This allows you to maintain and synchronize a local store of a user's messages withouthaving to fetch the entire set of messages from the server every time. + * Get a set of messages that were added, deleted, or updated in a specified folder. A delta function call for messages in a folder is similar to a GET request, except that by appropriatelyapplying state tokens in one or more of these calls, you can [query for incremental changes in the messages inthat folder](/graph/delta-query-messages). Using deltas allows you toincrementally maintain and synchronize a local store of a user's messages. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/MailFolders/Item/Messages/Delta/DeltaRequestBuilder.php b/src/Generated/Users/Item/MailFolders/Item/Messages/Delta/DeltaRequestBuilder.php index 41e07aa1265..9be8adf0a0d 100644 --- a/src/Generated/Users/Item/MailFolders/Item/Messages/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Users/Item/MailFolders/Item/Messages/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of messages that have been added, deleted, or updated in a specified folder. A delta function call for messages in a folder is similar to a GET request, except that by appropriatelyapplying state tokens in one or more of these calls, you can [query for incremental changes in the messages inthat folder](/graph/delta-query-messages). This allows you to maintain and synchronize a local store of a user's messages withouthaving to fetch the entire set of messages from the server every time. + * Get a set of messages that were added, deleted, or updated in a specified folder. A delta function call for messages in a folder is similar to a GET request, except that by appropriatelyapplying state tokens in one or more of these calls, you can [query for incremental changes in the messages inthat folder](/graph/delta-query-messages). Using deltas allows you toincrementally maintain and synchronize a local store of a user's messages. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of messages that have been added, deleted, or updated in a specified folder. A delta function call for messages in a folder is similar to a GET request, except that by appropriatelyapplying state tokens in one or more of these calls, you can [query for incremental changes in the messages inthat folder](/graph/delta-query-messages). This allows you to maintain and synchronize a local store of a user's messages withouthaving to fetch the entire set of messages from the server every time. + * Get a set of messages that were added, deleted, or updated in a specified folder. A delta function call for messages in a folder is similar to a GET request, except that by appropriatelyapplying state tokens in one or more of these calls, you can [query for incremental changes in the messages inthat folder](/graph/delta-query-messages). Using deltas allows you toincrementally maintain and synchronize a local store of a user's messages. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/MailFolders/Item/Messages/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/MailFolders/Item/Messages/Delta/DeltaRequestBuilderGetQueryParameters.php index 1a718f2a2ae..ac49c20494b 100644 --- a/src/Generated/Users/Item/MailFolders/Item/Messages/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/MailFolders/Item/Messages/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of messages that have been added, deleted, or updated in a specified folder. A delta function call for messages in a folder is similar to a GET request, except that by appropriatelyapplying state tokens in one or more of these calls, you can [query for incremental changes in the messages inthat folder](/graph/delta-query-messages). This allows you to maintain and synchronize a local store of a user's messages withouthaving to fetch the entire set of messages from the server every time. + * Get a set of messages that were added, deleted, or updated in a specified folder. A delta function call for messages in a folder is similar to a GET request, except that by appropriatelyapplying state tokens in one or more of these calls, you can [query for incremental changes in the messages inthat folder](/graph/delta-query-messages). Using deltas allows you toincrementally maintain and synchronize a local store of a user's messages. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/Messages/Delta/DeltaRequestBuilder.php b/src/Generated/Users/Item/Messages/Delta/DeltaRequestBuilder.php index ccbf31c283f..3dbe3d660e2 100644 --- a/src/Generated/Users/Item/Messages/Delta/DeltaRequestBuilder.php +++ b/src/Generated/Users/Item/Messages/Delta/DeltaRequestBuilder.php @@ -30,7 +30,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * Get a set of messages that have been added, deleted, or updated in a specified folder. A delta function call for messages in a folder is similar to a GET request, except that by appropriatelyapplying state tokens in one or more of these calls, you can [query for incremental changes in the messages inthat folder](/graph/delta-query-messages). This allows you to maintain and synchronize a local store of a user's messages withouthaving to fetch the entire set of messages from the server every time. + * Get a set of messages that were added, deleted, or updated in a specified folder. A delta function call for messages in a folder is similar to a GET request, except that by appropriatelyapplying state tokens in one or more of these calls, you can [query for incremental changes in the messages inthat folder](/graph/delta-query-messages). Using deltas allows you toincrementally maintain and synchronize a local store of a user's messages. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -45,7 +45,7 @@ public function get(?DeltaRequestBuilderGetRequestConfiguration $requestConfigur } /** - * Get a set of messages that have been added, deleted, or updated in a specified folder. A delta function call for messages in a folder is similar to a GET request, except that by appropriatelyapplying state tokens in one or more of these calls, you can [query for incremental changes in the messages inthat folder](/graph/delta-query-messages). This allows you to maintain and synchronize a local store of a user's messages withouthaving to fetch the entire set of messages from the server every time. + * Get a set of messages that were added, deleted, or updated in a specified folder. A delta function call for messages in a folder is similar to a GET request, except that by appropriatelyapplying state tokens in one or more of these calls, you can [query for incremental changes in the messages inthat folder](/graph/delta-query-messages). Using deltas allows you toincrementally maintain and synchronize a local store of a user's messages. * @param DeltaRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/Messages/Delta/DeltaRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/Messages/Delta/DeltaRequestBuilderGetQueryParameters.php index 6369d9bb5b3..1fdf9de3084 100644 --- a/src/Generated/Users/Item/Messages/Delta/DeltaRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/Messages/Delta/DeltaRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Get a set of messages that have been added, deleted, or updated in a specified folder. A delta function call for messages in a folder is similar to a GET request, except that by appropriatelyapplying state tokens in one or more of these calls, you can [query for incremental changes in the messages inthat folder](/graph/delta-query-messages). This allows you to maintain and synchronize a local store of a user's messages withouthaving to fetch the entire set of messages from the server every time. + * Get a set of messages that were added, deleted, or updated in a specified folder. A delta function call for messages in a folder is similar to a GET request, except that by appropriatelyapplying state tokens in one or more of these calls, you can [query for incremental changes in the messages inthat folder](/graph/delta-query-messages). Using deltas allows you toincrementally maintain and synchronize a local store of a user's messages. */ class DeltaRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/Onenote/Notebooks/Item/NotebookItemRequestBuilder.php b/src/Generated/Users/Item/Onenote/Notebooks/Item/NotebookItemRequestBuilder.php index 3555fefa196..47f5b4114e1 100644 --- a/src/Generated/Users/Item/Onenote/Notebooks/Item/NotebookItemRequestBuilder.php +++ b/src/Generated/Users/Item/Onenote/Notebooks/Item/NotebookItemRequestBuilder.php @@ -69,7 +69,7 @@ public function delete(?NotebookItemRequestBuilderDeleteRequestConfiguration $re } /** - * The collection of OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The collection of OneNote notebooks that the user or group owns. Read-only. Nullable. * @param NotebookItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -116,7 +116,7 @@ public function toDeleteRequestInformation(?NotebookItemRequestBuilderDeleteRequ } /** - * The collection of OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The collection of OneNote notebooks that the user or group owns. Read-only. Nullable. * @param NotebookItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/Onenote/Notebooks/Item/NotebookItemRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/Onenote/Notebooks/Item/NotebookItemRequestBuilderGetQueryParameters.php index d51a253d3f2..a75bc8c9850 100644 --- a/src/Generated/Users/Item/Onenote/Notebooks/Item/NotebookItemRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/Onenote/Notebooks/Item/NotebookItemRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * The collection of OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The collection of OneNote notebooks that the user or group owns. Read-only. Nullable. */ class NotebookItemRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/Onenote/Notebooks/NotebooksRequestBuilder.php b/src/Generated/Users/Item/Onenote/Notebooks/NotebooksRequestBuilder.php index 05e59b3ca95..21a795081fc 100644 --- a/src/Generated/Users/Item/Onenote/Notebooks/NotebooksRequestBuilder.php +++ b/src/Generated/Users/Item/Onenote/Notebooks/NotebooksRequestBuilder.php @@ -61,7 +61,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * The collection of OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The collection of OneNote notebooks that the user or group owns. Read-only. Nullable. * @param NotebooksRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -99,7 +99,7 @@ public function post(Notebook $body, ?NotebooksRequestBuilderPostRequestConfigur } /** - * The collection of OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The collection of OneNote notebooks that the user or group owns. Read-only. Nullable. * @param NotebooksRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/Onenote/Notebooks/NotebooksRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/Onenote/Notebooks/NotebooksRequestBuilderGetQueryParameters.php index ca489c215df..58e9305bb39 100644 --- a/src/Generated/Users/Item/Onenote/Notebooks/NotebooksRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/Onenote/Notebooks/NotebooksRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * The collection of OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The collection of OneNote notebooks that the user or group owns. Read-only. Nullable. */ class NotebooksRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/Onenote/Pages/Item/OnenotePageItemRequestBuilder.php b/src/Generated/Users/Item/Onenote/Pages/Item/OnenotePageItemRequestBuilder.php index 88557182156..c96c8adec14 100644 --- a/src/Generated/Users/Item/Onenote/Pages/Item/OnenotePageItemRequestBuilder.php +++ b/src/Generated/Users/Item/Onenote/Pages/Item/OnenotePageItemRequestBuilder.php @@ -93,7 +93,7 @@ public function delete(?OnenotePageItemRequestBuilderDeleteRequestConfiguration } /** - * The pages in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The pages in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @param OnenotePageItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -140,7 +140,7 @@ public function toDeleteRequestInformation(?OnenotePageItemRequestBuilderDeleteR } /** - * The pages in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The pages in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @param OnenotePageItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/Onenote/Pages/Item/OnenotePageItemRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/Onenote/Pages/Item/OnenotePageItemRequestBuilderGetQueryParameters.php index fd09cab05b4..88c1193fdba 100644 --- a/src/Generated/Users/Item/Onenote/Pages/Item/OnenotePageItemRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/Onenote/Pages/Item/OnenotePageItemRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * The pages in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The pages in all OneNote notebooks that the user or group owns. Read-only. Nullable. */ class OnenotePageItemRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/Onenote/Pages/PagesRequestBuilder.php b/src/Generated/Users/Item/Onenote/Pages/PagesRequestBuilder.php index e296125df1d..5dafcafc81b 100644 --- a/src/Generated/Users/Item/Onenote/Pages/PagesRequestBuilder.php +++ b/src/Generated/Users/Item/Onenote/Pages/PagesRequestBuilder.php @@ -52,7 +52,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * The pages in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The pages in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @param PagesRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -81,7 +81,7 @@ public function post(OnenotePage $body, ?PagesRequestBuilderPostRequestConfigura } /** - * The pages in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The pages in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @param PagesRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/Onenote/Pages/PagesRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/Onenote/Pages/PagesRequestBuilderGetQueryParameters.php index 72358f07872..94b553b3b3c 100644 --- a/src/Generated/Users/Item/Onenote/Pages/PagesRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/Onenote/Pages/PagesRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * The pages in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The pages in all OneNote notebooks that the user or group owns. Read-only. Nullable. */ class PagesRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/Onenote/SectionGroups/Item/SectionGroupItemRequestBuilder.php b/src/Generated/Users/Item/Onenote/SectionGroups/Item/SectionGroupItemRequestBuilder.php index d04ed75a84a..e893cb52c5e 100644 --- a/src/Generated/Users/Item/Onenote/SectionGroups/Item/SectionGroupItemRequestBuilder.php +++ b/src/Generated/Users/Item/Onenote/SectionGroups/Item/SectionGroupItemRequestBuilder.php @@ -77,7 +77,7 @@ public function delete(?SectionGroupItemRequestBuilderDeleteRequestConfiguration } /** - * The section groups in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The section groups in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @param SectionGroupItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -124,7 +124,7 @@ public function toDeleteRequestInformation(?SectionGroupItemRequestBuilderDelete } /** - * The section groups in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The section groups in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @param SectionGroupItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/Onenote/SectionGroups/Item/SectionGroupItemRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/Onenote/SectionGroups/Item/SectionGroupItemRequestBuilderGetQueryParameters.php index 8e2cc062f41..68c18ab8639 100644 --- a/src/Generated/Users/Item/Onenote/SectionGroups/Item/SectionGroupItemRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/Onenote/SectionGroups/Item/SectionGroupItemRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * The section groups in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The section groups in all OneNote notebooks that the user or group owns. Read-only. Nullable. */ class SectionGroupItemRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/Onenote/SectionGroups/SectionGroupsRequestBuilder.php b/src/Generated/Users/Item/Onenote/SectionGroups/SectionGroupsRequestBuilder.php index 993d677f2cf..767feb506a4 100644 --- a/src/Generated/Users/Item/Onenote/SectionGroups/SectionGroupsRequestBuilder.php +++ b/src/Generated/Users/Item/Onenote/SectionGroups/SectionGroupsRequestBuilder.php @@ -52,7 +52,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * The section groups in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The section groups in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @param SectionGroupsRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -81,7 +81,7 @@ public function post(SectionGroup $body, ?SectionGroupsRequestBuilderPostRequest } /** - * The section groups in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The section groups in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @param SectionGroupsRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/Onenote/SectionGroups/SectionGroupsRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/Onenote/SectionGroups/SectionGroupsRequestBuilderGetQueryParameters.php index c1e3fe36c90..b88d6a5212d 100644 --- a/src/Generated/Users/Item/Onenote/SectionGroups/SectionGroupsRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/Onenote/SectionGroups/SectionGroupsRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * The section groups in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The section groups in all OneNote notebooks that the user or group owns. Read-only. Nullable. */ class SectionGroupsRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/Onenote/Sections/Item/OnenoteSectionItemRequestBuilder.php b/src/Generated/Users/Item/Onenote/Sections/Item/OnenoteSectionItemRequestBuilder.php index 16f19a34140..640f7015bc4 100644 --- a/src/Generated/Users/Item/Onenote/Sections/Item/OnenoteSectionItemRequestBuilder.php +++ b/src/Generated/Users/Item/Onenote/Sections/Item/OnenoteSectionItemRequestBuilder.php @@ -85,7 +85,7 @@ public function delete(?OnenoteSectionItemRequestBuilderDeleteRequestConfigurati } /** - * The sections in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The sections in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @param OnenoteSectionItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -132,7 +132,7 @@ public function toDeleteRequestInformation(?OnenoteSectionItemRequestBuilderDele } /** - * The sections in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The sections in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @param OnenoteSectionItemRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/Onenote/Sections/Item/OnenoteSectionItemRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/Onenote/Sections/Item/OnenoteSectionItemRequestBuilderGetQueryParameters.php index c032c35ee1e..de77e4fde7e 100644 --- a/src/Generated/Users/Item/Onenote/Sections/Item/OnenoteSectionItemRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/Onenote/Sections/Item/OnenoteSectionItemRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * The sections in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The sections in all OneNote notebooks that the user or group owns. Read-only. Nullable. */ class OnenoteSectionItemRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/Onenote/Sections/SectionsRequestBuilder.php b/src/Generated/Users/Item/Onenote/Sections/SectionsRequestBuilder.php index 4c86b25298a..688a6736237 100644 --- a/src/Generated/Users/Item/Onenote/Sections/SectionsRequestBuilder.php +++ b/src/Generated/Users/Item/Onenote/Sections/SectionsRequestBuilder.php @@ -52,7 +52,7 @@ public function __construct($pathParametersOrRawUrl, RequestAdapter $requestAdap } /** - * The sections in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The sections in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @param SectionsRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception @@ -81,7 +81,7 @@ public function post(OnenoteSection $body, ?SectionsRequestBuilderPostRequestCon } /** - * The sections in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The sections in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @param SectionsRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/Onenote/Sections/SectionsRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/Onenote/Sections/SectionsRequestBuilderGetQueryParameters.php index 8d87f0edabd..6c6f3f4652e 100644 --- a/src/Generated/Users/Item/Onenote/Sections/SectionsRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/Onenote/Sections/SectionsRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * The sections in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * The sections in all OneNote notebooks that the user or group owns. Read-only. Nullable. */ class SectionsRequestBuilderGetQueryParameters { diff --git a/src/Generated/Users/Item/Presence/PresenceRequestBuilder.php b/src/Generated/Users/Item/Presence/PresenceRequestBuilder.php index eb801dc44dc..0e6459ae875 100644 --- a/src/Generated/Users/Item/Presence/PresenceRequestBuilder.php +++ b/src/Generated/Users/Item/Presence/PresenceRequestBuilder.php @@ -85,11 +85,11 @@ public function delete(?PresenceRequestBuilderDeleteRequestConfiguration $reques } /** - * Set a presence status message for a user. An optional expiration date and time can be supplied. + * Get a user's presence information. * @param PresenceRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return Promise * @throws Exception - * @link https://learn.microsoft.com/graph/api/presence-setstatusmessage?view=graph-rest-beta Find more info here + * @link https://learn.microsoft.com/graph/api/presence-get?view=graph-rest-beta Find more info here */ public function get(?PresenceRequestBuilderGetRequestConfiguration $requestConfiguration = null): Promise { $requestInfo = $this->toGetRequestInformation($requestConfiguration); @@ -133,7 +133,7 @@ public function toDeleteRequestInformation(?PresenceRequestBuilderDeleteRequestC } /** - * Set a presence status message for a user. An optional expiration date and time can be supplied. + * Get a user's presence information. * @param PresenceRequestBuilderGetRequestConfiguration|null $requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return RequestInformation */ diff --git a/src/Generated/Users/Item/Presence/PresenceRequestBuilderGetQueryParameters.php b/src/Generated/Users/Item/Presence/PresenceRequestBuilderGetQueryParameters.php index 4b7120c44ba..e1daf202f6a 100644 --- a/src/Generated/Users/Item/Presence/PresenceRequestBuilderGetQueryParameters.php +++ b/src/Generated/Users/Item/Presence/PresenceRequestBuilderGetQueryParameters.php @@ -5,7 +5,7 @@ use Microsoft\Kiota\Abstractions\QueryParameter; /** - * Set a presence status message for a user. An optional expiration date and time can be supplied. + * Get a user's presence information. */ class PresenceRequestBuilderGetQueryParameters { diff --git a/src/Generated/kiota-lock.json b/src/Generated/kiota-lock.json index bf7040be31d..9c7a4023f21 100644 --- a/src/Generated/kiota-lock.json +++ b/src/Generated/kiota-lock.json @@ -1,8 +1,8 @@ { - "descriptionHash": "C77E5CC6680E71997C77D4B497647030E3B6D51B37B16200F42FA2DB4238160C5FD8825BB6575991A5173DBE083163A1607E39644BDC1AE10B0562F5C8E58B3A", + "descriptionHash": "77254B0BD52910D9C305EC3E0405E2EB4BED8A7AEB257E670B2B233A135FD5BE50E8EE45E035F226EF613845E0E2616DBF0B7526EE9B02CD6A66C0DBF1D0605C", "descriptionLocation": "../../msgraph-metadata/clean_beta_openapi/openapi.yaml", "lockFileVersion": "1.0.0", - "kiotaVersion": "1.21.0", + "kiotaVersion": "1.22.0", "clientClassName": "BaseGraphClient", "typeAccessModifier": "Public", "clientNamespaceName": "Microsoft\\Graph\\Beta\\Generated",