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/active-directory/saas-apps/icims-tutorial.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
@@ -27,7 +27,7 @@ In this tutorial, you'll learn how to integrate ICIMS with Azure Active Director
27
27
* Enable your users to be automatically signed-in to ICIMS with their Azure AD accounts.
28
28
* Manage your accounts in one central location - the Azure portal.
29
29
30
-
To learn more about SaaS app integration with Azure AD, see [What is application access and single sign-on with Azure Active Directory](https://docs.microsoft.com/azure/active-directory/what-is-single-sign-on).
30
+
To learn more about SaaS app integration with Azure AD, see [What is application access and single sign-on with Azure Active Directory](https://docs.microsoft.com/azure/active-directory/manage-apps/what-is-single-sign-on).
31
31
32
32
## Prerequisites
33
33
@@ -147,7 +147,7 @@ When you click the ICIMS tile in the Access Panel, you should be automatically s
147
147
148
148
-[ List of Tutorials on How to Integrate SaaS Apps with Azure Active Directory ](https://docs.microsoft.com/azure/active-directory/active-directory-saas-tutorial-list)
149
149
150
-
-[What is application access and single sign-on with Azure Active Directory? ](https://docs.microsoft.com/azure/active-directory/what-is-single-sign-on)
150
+
-[What is application access and single sign-on with Azure Active Directory? ](https://docs.microsoft.com/azure/active-directory/manage-apps/what-is-single-sign-on)
151
151
152
152
-[What is conditional access in Azure Active Directory?](https://docs.microsoft.com/azure/active-directory/conditional-access/overview)
Copy file name to clipboardExpand all lines: articles/active-directory/saas-apps/opsgenie-tutorial.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
@@ -26,7 +26,7 @@ In this tutorial, you'll learn how to integrate OpsGenie with Azure Active Direc
26
26
* Enable your users to be automatically signed-in to OpsGenie with their Azure AD accounts.
27
27
* Manage your accounts in one central location - the Azure portal.
28
28
29
-
To learn more about SaaS app integration with Azure AD, see [What is application access and single sign-on with Azure Active Directory](https://docs.microsoft.com/azure/active-directory/what-is-single-sign-on).
29
+
To learn more about SaaS app integration with Azure AD, see [What is application access and single sign-on with Azure Active Directory](https://docs.microsoft.com/azure/active-directory/manage-apps/what-is-single-sign-on).
30
30
31
31
## Prerequisites
32
32
@@ -192,7 +192,7 @@ When you click the OpsGenie tile in the Access Panel, you should be automaticall
192
192
193
193
-[ List of Tutorials on How to Integrate SaaS Apps with Azure Active Directory ](https://docs.microsoft.com/azure/active-directory/active-directory-saas-tutorial-list)
194
194
195
-
-[What is application access and single sign-on with Azure Active Directory? ](https://docs.microsoft.com/azure/active-directory/what-is-single-sign-on)
195
+
-[What is application access and single sign-on with Azure Active Directory? ](https://docs.microsoft.com/azure/active-directory/manage-apps/what-is-single-sign-on)
196
196
197
197
-[What is conditional access in Azure Active Directory?](https://docs.microsoft.com/azure/active-directory/conditional-access/overview)
Copy file name to clipboardExpand all lines: articles/api-management/api-management-configuration-repository-git.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,7 +51,7 @@ To view and configure your Git configuration settings, you can click the **Secur
51
51
>
52
52
>
53
53
54
-
For information on enabling or disabling Git access using the REST API, see [Enable or disable Git access using the REST API](/rest/api/apimanagement/2019-01-01/tenantaccess?EnableGit).
54
+
For information on enabling or disabling Git access using the REST API, see [Enable or disable Git access using the REST API](/rest/api/apimanagement/2019-12-01/tenantaccess?EnableGit).
55
55
56
56
## To save the service configuration to the Git repository
57
57
@@ -63,7 +63,7 @@ After a few moments the configuration is saved, and the configuration status of
63
63
64
64
Once the configuration is saved to the repository, it can be cloned.
65
65
66
-
For information on performing this operation using the REST API, see [Commit configuration snapshot using the REST API](/rest/api/apimanagement/2019-01-01/tenantaccess?CommitSnapshot).
66
+
For information on performing this operation using the REST API, see [Commit configuration snapshot using the REST API](/rest/api/apimanagement/2019-12-01/tenantaccess?CommitSnapshot).
67
67
68
68
## To clone the repository to your local machine
69
69
@@ -137,7 +137,7 @@ git push
137
137
138
138
Once your local changes are committed and pushed to the server repository, you can deploy them to your API Management service instance.
139
139
140
-
For information on performing this operation using the REST API, see [Deploy Git changes to configuration database using the REST API](https://docs.microsoft.com/rest/api/apimanagement/2019-01-01/tenantconfiguration).
140
+
For information on performing this operation using the REST API, see [Deploy Git changes to configuration database using the REST API](https://docs.microsoft.com/rest/api/apimanagement/2019-12-01/tenantconfiguration).
141
141
142
142
## File and folder structure reference of local Git repository
143
143
@@ -167,9 +167,9 @@ These files can be created, deleted, edited, and managed on your local file syst
167
167
> [!NOTE]
168
168
> The following entities are not contained in the Git repository and cannot be configured using Git.
@@ -217,14 +217,14 @@ The final setting, `$ref-policy`, maps to the global policy statements file for
217
217
### apis folder
218
218
The `apis` folder contains a folder for each API in the service instance, which contains the following items.
219
219
220
-
*`apis\<api name>\configuration.json` - this is the configuration for the API and contains information about the backend service URL and the operations. This is the same information that would be returned if you were to call [Get a specific API](https://docs.microsoft.com/rest/api/apimanagement/2019-01-01/apis/get) with `export=true` in `application/json` format.
220
+
*`apis\<api name>\configuration.json` - this is the configuration for the API and contains information about the backend service URL and the operations. This is the same information that would be returned if you were to call [Get a specific API](https://docs.microsoft.com/rest/api/apimanagement/2019-12-01/apis/get) with `export=true` in `application/json` format.
221
221
*`apis\<api name>\api.description.html` - this is the description of the API and corresponds to the `description` property of the [API entity](https://docs.microsoft.com/java/api/com.microsoft.azure.storage.table.entityproperty).
222
222
*`apis\<api name>\operations\` - this folder contains `<operation name>.description.html` files that map to the operations in the API. Each file contains the description of a single operation in the API, which maps to the `description` property of the [operation entity](https://docs.microsoft.com/rest/api/visualstudio/operations/list#operationproperties) in the REST API.
223
223
224
224
### groups folder
225
225
The `groups` folder contains a folder for each group defined in the service instance.
226
226
227
-
*`groups\<group name>\configuration.json` - this is the configuration for the group. This is the same information that would be returned if you were to call the [Get a specific group](https://docs.microsoft.com/rest/api/apimanagement/2019-01-01/group/get) operation.
227
+
*`groups\<group name>\configuration.json` - this is the configuration for the group. This is the same information that would be returned if you were to call the [Get a specific group](https://docs.microsoft.com/rest/api/apimanagement/2019-12-01/group/get) operation.
228
228
*`groups\<group name>\description.html` - this is the description of the group and corresponds to the `description` property of the [group entity](https://docs.microsoft.com/rest/api/apimanagement/apimanagementrest/azure-api-management-rest-api-group-entity).
229
229
230
230
### policies folder
@@ -244,7 +244,7 @@ The `portalStyles` folder contains configuration and style sheets for developer
244
244
### products folder
245
245
The `products` folder contains a folder for each product defined in the service instance.
246
246
247
-
*`products\<product name>\configuration.json` - this is the configuration for the product. This is the same information that would be returned if you were to call the [Get a specific product](https://docs.microsoft.com/rest/api/apimanagement/2019-01-01/product/get) operation.
247
+
*`products\<product name>\configuration.json` - this is the configuration for the product. This is the same information that would be returned if you were to call the [Get a specific product](https://docs.microsoft.com/rest/api/apimanagement/2019-12-01/product/get) operation.
248
248
*`products\<product name>\product.description.html` - this is the description of the product and corresponds to the `description` property of the [product entity](https://docs.microsoft.com/rest/api/apimanagement/apimanagementrest/azure-api-management-rest-api-product-entity) in the REST API.
Copy file name to clipboardExpand all lines: articles/api-management/api-management-howto-add-products.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
@@ -81,7 +81,7 @@ Developers must first subscribe to a product to get access to the API. When they
81
81
4. Choose an API and click **Select**.
82
82
83
83
> [!TIP]
84
-
> You can create or update user's subscription to a *Product* with custom subscription keys [through REST API](https://docs.microsoft.com/rest/api/apimanagement/2019-01-01/subscription/createorupdate) or PowerShell command.
84
+
> You can create or update user's subscription to a *Product* with custom subscription keys [through REST API](https://docs.microsoft.com/rest/api/apimanagement/2019-12-01/subscription/createorupdate) or PowerShell command.
> Behind the scene, a [Logger](https://docs.microsoft.com/rest/api/apimanagement/2019-01-01/logger/createorupdate) entity is created in your API Management instance, containing the Instrumentation Key of the Application Insights instance.
51
+
> Behind the scene, a [Logger](https://docs.microsoft.com/rest/api/apimanagement/2019-12-01/logger/createorupdate) entity is created in your API Management instance, containing the Instrumentation Key of the Application Insights instance.
52
52
53
53
## Enable Application Insights logging for your API
54
54
@@ -67,7 +67,7 @@ Before you can use Azure Application Insights, you first need to create an insta
67
67
> Overriding the default value **0** in the **First bytes of body** field may significantly decrease the performance of your APIs.
68
68
69
69
> [!NOTE]
70
-
> Behind the scene, a [Diagnostic](https://docs.microsoft.com/rest/api/apimanagement/2019-01-01/diagnostic/createorupdate) entity named 'applicationinsights' is created at the API level.
70
+
> Behind the scene, a [Diagnostic](https://docs.microsoft.com/rest/api/apimanagement/2019-12-01/diagnostic/createorupdate) entity named 'applicationinsights' is created at the API level.
Copy file name to clipboardExpand all lines: articles/api-management/api-management-howto-create-or-invite-developers.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
@@ -17,7 +17,7 @@ ms.author: apimpm
17
17
---
18
18
# How to manage user accounts in Azure API Management
19
19
20
-
In API Management, developers are the users of the APIs that you expose using API Management. This guide shows to how to create and invite developers to use the APIs and products that you make available to them with your API Management instance. For information on managing user accounts programmatically, see the [User entity](https://docs.microsoft.com/rest/api/apimanagement/2019-01-01/user) documentation in the [API Management REST](/rest/api/apimanagement/) reference.
20
+
In API Management, developers are the users of the APIs that you expose using API Management. This guide shows to how to create and invite developers to use the APIs and products that you make available to them with your API Management instance. For information on managing user accounts programmatically, see the [User entity](https://docs.microsoft.com/rest/api/apimanagement/2019-12-01/user) documentation in the [API Management REST](/rest/api/apimanagement/) reference.
Copy file name to clipboardExpand all lines: articles/api-management/api-management-howto-disaster-recovery-backup-restore.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
@@ -127,7 +127,7 @@ Replace `{tenant id}`, `{application id}`, and `{redirect uri}` using the follow
127
127
128
128
## Calling the backup and restore operations
129
129
130
-
The REST APIs are [Api Management Service - Backup](/rest/api/apimanagement/2019-01-01/apimanagementservice/backup) and [Api Management Service - Restore](/rest/api/apimanagement/2019-01-01/apimanagementservice/restore).
130
+
The REST APIs are [Api Management Service - Backup](/rest/api/apimanagement/2019-12-01/apimanagementservice/backup) and [Api Management Service - Restore](/rest/api/apimanagement/2019-12-01/apimanagementservice/restore).
131
131
132
132
Before calling the "backup and restore" operations described in the following sections, set the authorization request header for your REST call.
Copy file name to clipboardExpand all lines: articles/api-management/api-management-howto-log-event-hubs.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,9 +26,9 @@ This article is a companion to the [Integrate Azure API Management with Event Hu
26
26
For detailed steps on how to create an event hub and get connection strings that you need to send and receive events to and from the Event Hub, see [Create an Event Hubs namespace and an event hub using the Azure portal](https://docs.microsoft.com/azure/event-hubs/event-hubs-create).
27
27
28
28
## Create an API Management logger
29
-
Now that you have an Event Hub, the next step is to configure a [Logger](https://docs.microsoft.com/rest/api/apimanagement/2019-01-01/logger) in your API Management service so that it can log events to the Event Hub.
29
+
Now that you have an Event Hub, the next step is to configure a [Logger](https://docs.microsoft.com/rest/api/apimanagement/2019-12-01/logger) in your API Management service so that it can log events to the Event Hub.
30
30
31
-
API Management loggers are configured using the [API Management REST API](https://aka.ms/apimapi). For detailed request examples, see [how to create Loggers](https://docs.microsoft.com/rest/api/apimanagement/2019-01-01/logger/createorupdate).
31
+
API Management loggers are configured using the [API Management REST API](https://aka.ms/apimapi). For detailed request examples, see [how to create Loggers](https://docs.microsoft.com/rest/api/apimanagement/2019-12-01/logger/createorupdate).
32
32
33
33
## Configure log-to-eventhubs policies
34
34
@@ -61,7 +61,7 @@ Click **Save** to save the updated policy configuration. As soon as it is saved
61
61
*[Receive messages with EventProcessorHost](../event-hubs/event-hubs-dotnet-standard-getstarted-receive-eph.md)
0 commit comments