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
Copy file name to clipboardExpand all lines: articles/ai-services/openai/concepts/understand-embeddings.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
@@ -15,7 +15,7 @@ ms.custom:
15
15
16
16
# Understand embeddings in Azure OpenAI Service
17
17
18
-
An embedding is a special format of data representation that machine learning models and algorithms can easily use. The embedding is an information dense representation of the semantic meaning of a piece of text. Each embedding is a vector of floating-point numbers, such that the distance between two embeddings in the vector space is correlated with semantic similarity between two inputs in the original format. For example, if two texts are similar, then their vector representations should also be similar. Embeddings power vector similarity search in Azure Databases such as [Azure Cosmos DB for MongoDB vCore](../../../cosmos-db/mongodb/vcore/vector-search.md) or [Azure Database for PostgreSQL - Flexible Server](../../../postgresql/flexible-server/how-to-use-pgvector.md).
18
+
An embedding is a special format of data representation that machine learning models and algorithms can easily use. The embedding is an information dense representation of the semantic meaning of a piece of text. Each embedding is a vector of floating-point numbers, such that the distance between two embeddings in the vector space is correlated with semantic similarity between two inputs in the original format. For example, if two texts are similar, then their vector representations should also be similar. Embeddings power vector similarity search in Azure Databases such as [Azure Cosmos DB for MongoDB vCore](../../../cosmos-db/mongodb/vcore/vector-search.md), [Azure SQL Database](/azure/azure-sql/database/ai-artificial-intelligence-intelligent-applications?view=azuresql&preserve-view=true#vector-search)or [Azure Database for PostgreSQL - Flexible Server](../../../postgresql/flexible-server/how-to-use-pgvector.md).
19
19
20
20
## Embedding models
21
21
@@ -38,4 +38,4 @@ An alternative method of identifying similar documents is to count the number of
38
38
## Next steps
39
39
40
40
* Learn more about using Azure OpenAI and embeddings to perform document search with our [embeddings tutorial](../tutorials/embeddings.md).
41
-
* Store your embeddings and perform vector (similarity) search using [Azure Cosmos DB for MongoDB vCore](../../../cosmos-db/mongodb/vcore/vector-search.md), [Azure Cosmos DB for NoSQL](../../../cosmos-db/rag-data-openai.md) or [Azure Database for PostgreSQL - Flexible Server](../../../postgresql/flexible-server/how-to-use-pgvector.md).
41
+
* Store your embeddings and perform vector (similarity) search using [Azure Cosmos DB for MongoDB vCore](../../../cosmos-db/mongodb/vcore/vector-search.md), [Azure Cosmos DB for NoSQL](../../../cosmos-db/rag-data-openai.md), [Azure SQL Database](/azure/azure-sql/database/ai-artificial-intelligence-intelligent-applications?view=azuresql&preserve-view=true#vector-search)or [Azure Database for PostgreSQL - Flexible Server](../../../postgresql/flexible-server/how-to-use-pgvector.md).
Copy file name to clipboardExpand all lines: articles/app-service/environment/how-to-migrate.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -305,7 +305,7 @@ This step takes three to six hours for v2 to v3 migrations and up to six hours f
305
305
>
306
306
> :::image type="content" source="./media/migration/migration-error-2.png" alt-text="Screenshot that shows the potential error notification after migration starts.":::
307
307
308
-
At this time, detailed migration statuses are available only when you're using the Azure CLI. For more information, see the [Azure CLI section for migrating to App Service Environment v3](#8-migrate-to-app-service-environment-v3-and-check-status).
308
+
At this time, detailed migration statuses are available only when you're using the Azure CLI. For more information, see the Azure CLI section for migrating to App Service Environment v3. You can check the status of the migration with the CLI even if you use the portal to do the migration.
309
309
310
310
When migration is complete, you have an App Service Environment v3 resource, and all of your apps are running in your new environment. You can confirm the environment's version by checking the **Configuration** page for your App Service Environment.
Copy file name to clipboardExpand all lines: articles/app-service/environment/migrate.md
+11Lines changed: 11 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -151,6 +151,17 @@ Migration requires a three to six hour service window for App Service Environmen
151
151
- If you can't support downtime, see the [side-by-side migration feature](side-by-side-migrate.md) or the [migration-alternatives](migration-alternatives.md#migrate-manually).
152
152
- The public addresses that are used by the App Service Environment change to the IPs generated during the IP generation step.
153
153
154
+
The following statuses are available during the migration process:
155
+
156
+
|Status |Description |
157
+
|------------|-------------|
158
+
|Validating and preparing the migration. |The platform is validating migration support and performing necessary checks. |
159
+
|Deploying App Service Environment v3 infrastructure. |Your new App Service Environment v3 infrastructure is provisioning. |
160
+
|Waiting for infrastructure to complete. |The platform is validating your new infrastructure and performing necessary checks. |
161
+
|Setting up networking. Migration downtime period has started. Applications are not accessible. |The platform is deleting your old infrastructure and moving all of your apps to your new App Service Environment v3. Your apps are down and aren't accepting traffic. |
162
+
|Running post migration validations. |The platform is performing necessary checks to ensure the migration succeeded. |
163
+
|Finalizing migration. |The platform is finalizing the migration. |
164
+
154
165
As in the IP generation step, you can't scale, modify your App Service Environment, or deploy apps to it during this process. When migration is complete, the apps that were on the old App Service Environment are running on the new App Service Environment v3.
Copy file name to clipboardExpand all lines: articles/communication-services/quickstarts/voice-video-calling/includes/get-started/get-started-android.md
+20-18Lines changed: 20 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,7 +36,7 @@ From Android Studio, select Start a new Android Studio project.
36
36
37
37
:::image type="content" source="../../media/android/studio-new-project.png" alt-text="Screenshot showing the 'Start a new Android Studio Project' button selected in Android Studio.":::
38
38
39
-
Select "Empty Activity" project template under "Phone and Tablet".
39
+
Select "Empty Views Activity" project template under "Phone and Tablet".
40
40
41
41
:::image type="content" source="../../media/android/studio-blank-activity.png" alt-text="Screenshot showing the 'Empty Activity' option selected in the Project Template Screen.":::
42
42
@@ -48,23 +48,21 @@ Select Minimum SDK of "API 26: Android 8.0 (Oreo)" or greater.
48
48
### Install the package
49
49
50
50
<!-- TODO: update with instructions on how to download, install and add package to project -->
51
-
Locate your project level build.gradle and make sure to add`mavenCentral()`to the list of repositories under `buildscript` and `allprojects`
51
+
Locate your project `settings.gradle.kts` and make sure to see`mavenCentral()`at the list of repositories under `pluginManagement` and `dependencyResolutionManagement`
Copy file name to clipboardExpand all lines: articles/communication-services/quickstarts/voice-video-calling/includes/get-started/get-started-windows.md
+58-8Lines changed: 58 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,7 +38,7 @@ In Visual Studio, create a new project with the **Blank App (Universal Windows)*
38
38
39
39
#### Install the package
40
40
41
-
Right select your project and go to `Manage Nuget Packages` to install `Azure.Communication.Calling.WindowsClient`[1.2.0-beta.1](https://www.nuget.org/packages/Azure.Communication.Calling.WindowsClient/1.2.0-beta.1) or superior. Make sure Include Preleased is checked.
41
+
Right select your project and go to `Manage Nuget Packages` to install `Azure.Communication.Calling.WindowsClient`[1.4.0](https://www.nuget.org/packages/Azure.Communication.Calling.WindowsClient/1.4.0) or superior. Make sure `Include Prerelease` is checked if you want to see the versions for public preview.
42
42
43
43
#### Request access
44
44
@@ -64,6 +64,9 @@ Open the `MainPage.xaml` of your project and add the `Grid` node to your `Page`:
You can build and run the code on Visual Studio. For solution platforms, we support `ARM64`, `x64` and `x86`.
398
+
You can build and run the code on Visual Studio. For solution platforms, we support `ARM64`, `x64`, and `x86`.
349
399
350
400
You can make an outbound call by providing a user ID in the text field and clicking the `Start Call/Join` button. Calling `8:echo123` connects you with an echo bot, this feature is great for getting started and verifying your audio devices are working.
351
401
@@ -572,7 +622,7 @@ Add the implementation to the `CallButton_Click` to start various kinds of calls
572
622
{
573
623
varcallString=CalleeTextBox.Text.Trim();
574
624
575
-
call=awaitStartAcsCallAsync(callString);
625
+
call=awaitStartCallAsync(callString);
576
626
if (call!=null)
577
627
{
578
628
call.StateChanged+=OnStateChangedAsync;
@@ -657,7 +707,7 @@ In the meeting join scenario, `JoinCallOptions` is made available to customize t
657
707
Once a `StartCallOptions` object is obtained, `CallAgent` can be used to initiate the Azure Communication Services call:
0 commit comments