You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|`context`|[`Api`](#ref-context-api): [`IApi`](#ref-iapi)<br /><br /> [`Deployment`](#ref-context-deployment)<br /><br /> Elapsed: `TimeSpan` - time interval between the value of `Timestamp` and current time<br /><br /> [`LastError`](#ref-context-lasterror)<br /><br /> [`Operation`](#ref-context-operation)<br /><br /> [`Product`](#ref-context-product)<br /><br /> [`Request`](#ref-context-request)<br /><br /> `RequestId`: `Guid` - unique request identifier<br /><br /> [`Response`](#ref-context-response)<br /><br /> [`Subscription`](#ref-context-subscription)<br /><br /> `Timestamp`: `DateTime` - point in time when request was received<br /><br /> `Tracing`: `bool` - indicates if tracing is on or off <br /><br /> [User](#ref-context-user)<br /><br /> [`Variables`](#ref-context-variables): `IReadOnlyDictionary<string, object>`<br /><br /> `void Trace(message: string)`|
Copy file name to clipboardExpand all lines: articles/azure-monitor/logs/basic-logs-configure.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -56,6 +56,7 @@ Configure a table for Basic logs if:
56
56
|[AMSKeyDeliveryRequests](/azure/azure-monitor/reference/tables/AMSKeyDeliveryRequests)| Azure Media Services HTTP request details for key, or license acquisition. |
57
57
|[AMSMediaAccountHealth](/azure/azure-monitor/reference/tables/AMSMediaAccountHealth)| Azure Media Services account health status. |
58
58
|[AMSStreamingEndpointRequests](/azure/azure-monitor/reference/tables/AMSStreamingEndpointRequests)| Azure Media Services information about requests to streaming endpoints. |
59
+
|[ASCDeviceEvents](/azure/azure-monitor/reference/tables/ASCDeviceEvents)| Azure Sphere devices operations, with information about event types, event categories, event classes, event descriptions etc. |
59
60
|[ContainerAppConsoleLogs](/azure/azure-monitor/reference/tables/containerappconsoleLogs)| Azure Container Apps logs, generated within a Container Apps environment. |
60
61
|[ContainerLogV2](/azure/azure-monitor/reference/tables/containerlogv2)| Used in [Container insights](../containers/container-insights-overview.md) and includes verbose text-based log records. |
61
62
|[DevCenterDiagnosticLogs](/azure/azure-monitor/reference/tables/DevCenterDiagnosticLogs)| Dev Center resources data plane audit logs. For example, dev boxes and environment stop, start, delete. |
Copy file name to clipboardExpand all lines: articles/cognitive-services/Speech-Service/how-to-custom-speech-test-and-train.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -95,6 +95,9 @@ A large training dataset is required to improve recognition. Generally, we recom
95
95
96
96
Audio files can have silence at the beginning and end of the recording. If possible, include at least a half-second of silence before and after speech in each sample file. Although audio with low recording volume or disruptive background noise is not helpful, it shouldn't limit or degrade your custom model. Always consider upgrading your microphones and signal processing hardware before gathering audio samples.
97
97
98
+
> [!IMPORTANT]
99
+
> For more information about the best practices of preparing human-labeled transcripts, see [Human-labeled transcripts with audio](how-to-custom-speech-human-labeled-transcriptions.md).
100
+
98
101
Custom Speech projects require audio files with these properties:
Copy file name to clipboardExpand all lines: articles/communications-gateway/interoperability.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,8 +44,8 @@ Azure Communications Gateway supports the Microsoft specifications for Certified
44
44
45
45
The Microsoft Phone System relies on information in SIP signaling to determine whether a call is:
46
46
47
-
- To a Teams Mobile Phone subscriber.
48
-
- From a Teams Mobile Phone subscriber or between two Teams Phone Mobile subscribers.
47
+
- To a Teams Phone Mobile subscriber.
48
+
- From a Teams Phone Mobile subscriber or between two Teams Phone Mobile subscribers.
49
49
50
50
Your core mobile network must supply this information to Azure Communications Gateway, by using unique trunks or by correctly populating an `X-MS-FMC` header as defined by the Teams Phone Mobile SIP specifications.
0 commit comments