Skip to content

Commit ba1fe10

Browse files
ttorblettorble
authored
Merge pull request #291715 from MicrosoftDocs/main
Publish to live, Tuesday 4 AM PST, 12/10
2 parents 7d1270d + ed4cb34 commit ba1fe10

File tree

7 files changed

+25
-91
lines changed

7 files changed

+25
-91
lines changed

‎articles/backup/backup-azure-afs-automation.md

Lines changed: 15 additions & 41 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Back up an Azure file share by using PowerShell
33
description: In this article, learn how to back up an Azure Files file share by using the Azure Backup service and PowerShell.
44
ms.topic: how-to
5-
ms.date: 07/18/2024
5+
ms.date: 12/10/2024
66
ms.custom: devx-track-azurepowershell
77
ms.service: azure-backup
88
author: AbhishekMallick-MS
@@ -152,45 +152,12 @@ A backup policy specifies the schedule for backups, and how long backup recovery
152152

153153
A backup policy is associated with at least one retention policy. A retention policy defines how long a recovery point is kept before it's deleted. You can configure backups with daily, weekly, monthly, or yearly retention. With multiple backups policy, you can also configure backups hourly retention.
154154

155-
**Choose a policy type**:
156-
157-
# [Daily backup policy](#tab/daily-backup-policy)
158-
159-
Here are some cmdlets for backup policies:
160-
161-
* View the default backup policy retention by using [Get-AzRecoveryServicesBackupRetentionPolicyObject](/powershell/module/az.recoveryservices/get-azrecoveryservicesbackupretentionpolicyobject).
162-
* View the default backup policy schedule by using [Get-AzRecoveryServicesBackupSchedulePolicyObject](/powershell/module/az.recoveryservices/get-azrecoveryservicesbackupschedulepolicyobject).
163-
* Create a new backup policy by using [New-AzRecoveryServicesBackupProtectionPolicy](/powershell/module/az.recoveryservices/set-azrecoveryservicesbackupprotectionpolicy). You enter the schedule and retention policy objects as input.
164-
165-
By default, a start time is defined in the schedule policy object. Use the following example to change the start time to the desired start time. The desired start time should be in Universal Coordinated Time (UTC). The example assumes that the desired start time is 01:00 AM UTC for daily backups.
166-
167-
```azurepowershell-interactive
168-
$schPol = Get-AzRecoveryServicesBackupSchedulePolicyObject -WorkloadType "AzureFiles"
169-
$UtcTime = Get-Date -Date "2019-03-20 01:30:00Z"
170-
$UtcTime = $UtcTime.ToUniversalTime()
171-
$schpol.ScheduleRunTimes[0] = $UtcTime
172-
```
173-
174-
> [!IMPORTANT]
175-
> You need to provide the start time in 30-minute multiples only. In the preceding example, it can be only "01:00:00" or "02:30:00". The start time can't be "01:15:00".
176-
177-
The following example stores the schedule policy and the retention policy in variables. It then uses those variables as parameters for a new policy (**NewAFSPolicy**). **NewAFSPolicy** takes a daily backup and retains it for 30 days.
178-
179-
```azurepowershell-interactive
180-
$schPol = Get-AzRecoveryServicesBackupSchedulePolicyObject -WorkloadType "AzureFiles"
181-
$retPol = Get-AzRecoveryServicesBackupRetentionPolicyObject -WorkloadType "AzureFiles"
182-
New-AzRecoveryServicesBackupProtectionPolicy -Name "NewAFSPolicy" -WorkloadType "AzureFiles" -RetentionPolicy $retPol -SchedulePolicy $schPol
183-
```
184-
185-
The output is similar to the following:
186-
187-
```azurepowershell-interactive
188-
Name WorkloadType BackupManagementType BackupTime DaysOfWeek
189-
---- ------------ -------------------- ---------- ----------
190-
NewAFSPolicy AzureFiles AzureStorage 10/24/2019 1:30:00 AM
191-
```
192-
193-
# [Multiple backups policy](#tab/multiple-backups-policy)
155+
>[!Important]
156+
>The following cmdlets are used for the Backup policies:
157+
>
158+
>- View the default backup policy retention by using `Get-AzRecoveryServicesBackupRetentionPolicyObject`.
159+
>- View the default backup policy schedule by using `Get-AzRecoveryServicesBackupSchedulePolicyObject`.
160+
>- Create a new backup policy by using `New-AzRecoveryServicesBackupProtectionPolicy`. Provide the schedule and retention policy objects as inputs.
194161
195162
To create a backup policy that configures multiple backups a day, follow these steps:
196163

@@ -230,6 +197,14 @@ To create a backup policy that configures multiple backups a day, follow these s
230197
$schPol.ScheduleRunTimeZone=$timeZone.Id
231198
```
232199

200+
To reate a policy with daily schedule, run the following cmdlet:
201+
202+
```azurepowershell
203+
$UtcTime = Get-Date -Date "2019-03-20 01:30:00Z"
204+
$UtcTime = $UtcTime.ToUniversalTime()
205+
$schpol.ScheduleRunTimes[0] = $UtcTime
206+
```
207+
233208
1. Fetch the retention policy object using following cmdlet:
234209

235210
```azurepowershell-interactive
@@ -260,7 +235,6 @@ To create a backup policy that configures multiple backups a day, follow these s
260235
testing AzureFiles AzureStorage Hourly 12/22/2021 8:00:00 AM 4 12 Russia Time Zone 11
261236
262237
```
263-
---
264238
265239
## Enable backup
266240

‎articles/communication-services/concepts/interop/guest/capabilities.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -124,8 +124,10 @@ This article describes which capabilities Azure Communication Services SDKs supp
124124
| | Apply [Watermark](/microsoftteams/watermark-meeting-content-video) over received video and screen sharing | ❌ |
125125
| Recording & transcription | Manage Teams cloud recording | ❌[6] |
126126
| | Receive information of call being cloud recorded | ✔️ |
127+
| | Give explicit consent to Teams cloud recording | ✔️ |
127128
| | Manage Teams transcription | ❌[6] |
128129
| | Receive information of call being transcribed | ✔️ |
130+
| | Give explicit consent to Teams transcription | ✔️ |
129131
| | Manage Teams closed captions | ✔️ |
130132
| | Support for compliance recording | ✔️ |
131133
| | [Azure Communication Services recording](../../voice-video-calling/call-recording.md) | ❌ |

‎articles/communication-services/concepts/interop/teams-user-calling.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -96,10 +96,10 @@ The following list presents the set of features that are currently available in
9696
| | Custom background image | ✔️ | ❌ | ❌ | ❌ |
9797
| Recording & transcription | Manage Teams cloud recording | ❌ | ❌ | ❌ | ❌ |
9898
| | Receive information of call being cloud recorded | ✔️ | ✔️ | ✔️ | ✔️ |
99-
| | Manage Teams local recording | ❌ | ❌ | ❌ | ❌ |
100-
| | Receive information of call being locally recorded | ✔️ | ✔️ | ✔️ | ✔️ |
99+
| | Give explicit consent to Teams cloud recording | ✔️ | ❌ | ❌ | ❌ |
101100
| | Manage Teams transcription | ❌ | ❌ | ❌ | ❌ |
102101
| | Receive information of call being transcribed | ✔️ | ✔️ | ✔️ | ✔️ |
102+
| | Give explicit consent to Teams transcription | ✔️ | ❌ | ❌ | ❌ |
103103
| | Manage Teams closed captions | ✔️ | ✔️ | ✔️ | ✔️ |
104104
| | Support for compliance recording | ✔️ | ✔️ | ✔️ | ✔️ |
105105
| Engagement | Raise and lower hand | ✔️ | ✔️ | ✔️ | ✔️ |

‎articles/communication-services/concepts/interop/teams-user/meeting-capabilities.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -94,8 +94,10 @@ The following list of capabilities is allowed when Microsoft 365 users participa
9494
| | Custom background image | ✔️ | ❌ | ❌ | ❌ |
9595
| Recording & transcription | Manage Teams convenient recording | ❌ | ❌ | ❌ | ❌ |
9696
| | Receive information of call being recorded | ✔️ | ✔️ | ✔️ | ✔️ |
97+
| | Give explicit consent to Teams cloud recording | ✔️ | ❌ | ❌ | ❌ |
9798
| | Manage Teams transcription | ❌ | ❌ | ❌ | ❌ |
9899
| | Receive information of call being transcribed | ✔️ | ✔️ | ✔️ | ✔️ |
100+
| | Give explicit consent to Teams transcribed | ✔️ | ❌ | ❌ | ❌ |
99101
| | Support for compliance recording | ✔️ | ✔️ | ✔️ | ✔️ |
100102
| | [Azure Communication Services recording](../../voice-video-calling/call-recording.md) | ❌ | ❌ | ❌ | ❌ |
101103
| Engagement | Raise and lower hand | ✔️ | ✔️ | ✔️ | ✔️ |

‎articles/communication-services/concepts/interop/teams-user/phone-capabilities.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -79,8 +79,10 @@ The following list of capabilities is supported for scenarios where at least one
7979
| | Render remote video stream | ✔️* |
8080
| Recording & transcription | Manage Teams convenient recording | ❌ |
8181
| | Receive information of call being recorded | ✔️ |
82+
| | Give explicit consent to Teams cloud recording | ✔️ |
8283
| | Manage Teams transcription | ❌ |
8384
| | Receive information of call being transcribed | ✔️ |
85+
| | Give explicit consent to Teams transcription | ✔️ |
8486
| | Support for compliance recording | ✔️ |
8587
| Media | Support for early media | ✔️ |
8688
| | Place a phone call honors location-based routing | ❌ |

‎articles/communications-gateway/media/azure-communications-gateway-overview.svg

Lines changed: 1 addition & 47 deletions
Loading

‎articles/frontdoor/front-door-diagnostics.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -82,7 +82,7 @@ Information about every request is logged into the access log. Each access log e
8282
| Endpoint | The domain name of the Azure Front Door endpoint, such as `contoso-123.z01.azurefd.net`. |
8383
| HttpStatusCode | The HTTP status code returned from Azure Front Door. If the request to the origin timed out, the value for the HttpStatusCode field is **0**. If the client closed the connection, the value for the HttpStatusCode field is **499**. |
8484
| Pop | The Azure Front Door edge point of presence (PoP) that responded to the user request. |
85-
| Cache Status | How the request was handled by the Azure Front Door cache. Possible values are: <ul><li>**HIT** and **REMOTE_HIT**: The HTTP request was served from the Azure Front Door cache.</li><li>**MISS**: The HTTP request was served from origin. </li><li> **PARTIAL_HIT**: Some of the bytes were served from the Front Door edge PoP cache, and other bytes were served from the origin. This status indicates an [object chunking](./front-door-caching.md#delivery-of-large-files) scenario. </li><li> **CACHE_NOCONFIG**: The request was forwarded without caching settings, including bypass scenarios. </li><li> **PRIVATE_NOSTORE**: There was no cache configured in the caching settings by the customer. </li><li> **N/A**: The request was denied by a signed URL or the Rules Engine.</li></ul> |
85+
| Cache Status | How the request was handled by the Azure Front Door cache. Possible values are: <ul><li>**HIT** and **REMOTE_HIT**: The HTTP request was served from the Azure Front Door cache.</li><li>**MISS**: The HTTP request was served from origin. </li><li> **PARTIAL_HIT**: Some of the bytes were served from the Front Door edge PoP cache, and other bytes were served from the origin. This status indicates an [object chunking](./front-door-caching.md#delivery-of-large-files) scenario. </li><li> **CACHE_NOCONFIG**: The request was forwarded without caching settings, including bypass scenarios. </li><li> **PRIVATE_NOSTORE**: There was no cache configured in the caching settings by the customer. </li><li> **N/A**: The request was denied by a signed URL or WAF rules.</li></ul> |
8686
| MatchedRulesSetName | The names of the Rules Engine rules that were processed. |
8787
| RouteName | The name of the route that the request matched. |
8888
| ClientPort | The IP port of the client that made the request. |

0 commit comments

Comments
 (0)