Skip to content

Commit e5164b2

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into fixVideos
2 parents 331cdb1 + c568cd9 commit e5164b2

File tree

2 files changed

+20
-16
lines changed

2 files changed

+20
-16
lines changed

articles/machine-learning/how-to-manage-models-mlflow.md

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -20,6 +20,14 @@ Azure Machine Learning supports MLflow for model management. This represents a c
2020

2121
[!INCLUDE [mlflow-prereqs](../../includes/machine-learning-mlflow-prereqs.md)]
2222

23+
* Some operations may be executed directly using the MLflow fluent API (`mlflow.<method>`). However, others may require to create an MLflow client, which allows to communicate with Azure Machine Learning in the MLflow protocol. You can create an `MlflowClient` object as follows. This tutorial will use the object `client` to refer to such MLflow client.
24+
25+
```python
26+
using mlflow
27+
28+
client = mlflow.tracking.MlflowClient()
29+
```
30+
2331
## Registering new models in the registry
2432

2533
### Creating models from an existing run
@@ -33,6 +41,9 @@ mlflow.register_model(f"runs:/{run_id}/{artifact_path}", model_name)
3341
> [!NOTE]
3442
> Models can only be registered to the registry in the same workspace where the run was tracked. Cross-workspace operations are not supported by the moment in Azure Machine Learning.
3543
44+
> [!TIP]
45+
> We recommend to register models from runs or using the method `mlflow.<flavor>.log_model` from inside the run as it keeps lineage from the job that generated the asset.
46+
3647
### Creating models from assets
3748

3849
If you have a folder with an MLModel MLflow model, then you can register it directly. There's no need for the model to be always in the context of a run. To do that you can use the URI schema `file://path/to/model` to register MLflow models stored in the local file system. Let's create a simple model using `Scikit-Learn` and save it in MLflow format in the local storage:
@@ -58,22 +69,11 @@ model_local_path = os.path.abspath("./regressor")
5869
mlflow.register_model(f"file://{model_local_path}", "local-model-test")
5970
```
6071

61-
> [!NOTE]
62-
> Notice how the model URI schema `file:/` requires absolute paths.
63-
6472
## Querying model registries
6573

6674
### Querying all the models in the registry
6775

68-
You can query all the registered models in the registry using the MLflow client with the method `list_registered_models`. The MLflow client is required to do all these operations.
69-
70-
```python
71-
using mlflow
72-
73-
client = mlflow.tracking.MlflowClient()
74-
```
75-
76-
The following sample prints all the model's names:
76+
You can query all the registered models in the registry using the MLflow client. The following sample prints all the model's names:
7777

7878
```python
7979
for model in client.search_registered_models():

articles/marketplace/isv-customer.md

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -81,14 +81,16 @@ Use this page to define private offer terms, notification contacts, and pricing
8181

8282
- **Customer Information** – Specify the billing account for the customer receiving this private offer. This will only be available to the configured customer billing account and the customer will need to be an owner or contributor or signatory on the billing account to accept the offer.
8383

84-
> [!NOTE]
85-
> Customers can find their billing account ID in 2 ways. 1) In the [Azure portal](https://aka.ms/PrivateOfferAzurePortal) under **Cost Management + Billing** **Properties** **ID**. A user in the customer organization should have access to the billing account to see the ID in Azure Portal. 2) If customer knows the subscription they plan to use for the purchase, click on **Subscriptions**, click on the relevant subscription **Properties** (or Billing Properties) **Billing Account ID**. See [Billing account scopes in the Azure portal](/azure/cost-management-billing/manage/view-all-accounts).
84+
> [!NOTE]
85+
> Customers can find their billing account ID in 2 ways. 1) In the [Azure portal](https://aka.ms/PrivateOfferAzurePortal) under **Cost Management + Billing** > **Properties** >**ID**. A user in the customer organization should have access to the billing account to see the ID in Azure Portal. 2) If the customer knows the subscription they plan to use for the purchase, click on **Subscriptions**, click on the relevant subscription **Properties** (or Billing Properties) **Billing Account ID**. See [Billing account scopes in the Azure portal](/azure/cost-management-billing/manage/view-all-accounts).
8686
8787
:::image type="content" source="media/isv-customer/customer-properties.png" alt-text="Shows the offer Properties tab in Partner Center.":::
8888

89-
- **Private offer terms** – Specify the duration, accept-by date, and terms:
89+
![Screenshot showing subscription name properties.](media/isv-customer/subscription-name-properties.png)
90+
9091

91-
- **Start date** – Choose **Accepted date** if you want the private offer to start as soon as the customer accepts it. If a private offer is extended to an existing customer of a Pay-as-you-go product, this will make the private price applicable for the entire month. To have your private offer start in an upcoming month, select **Specific month** and choose one. The start date for this option will always be the first day of the selected month.
92+
- **Private offer terms** – Specify the duration, accept-by date, and terms:
93+
- **Start date** – Choose **Accepted date** if you want the private offer to start as soon as the customer accepts it. If a private offer is extended to an existing customer of a Pay-as-you-go product, this will make the private price applicable for the entire month. To have your private offer start in an upcoming month, select **Specific month** and choose one. The start date for this option will always be the first day of the selected month.
9294
- **End date** – Choose the month for your private offer's **End date**. This will always be the last day of the selected month.
9395
- **Accept by** – Choose the expiration date for your private offer. Your customer must accept the private offer prior to this date.
9496
- **Terms and conditions** – Optionally, upload a PDF with terms and conditions your customer must accept as part of the private offer.
@@ -192,3 +194,5 @@ The payout amount and agency fee that Microsoft charges is based on the private
192194
- [ISV to Customer Private Offer Acceptance](https://www.youtube.com/watch?v=HWpLOOtfWZs)
193195
- [ISV to Customer Private Offer Purchase Experience](https://www.youtube.com/watch?v=mPX7gqdHqBk)
194196

197+
198+

0 commit comments

Comments
 (0)