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: src/content/blog/building-custom-copilots-in-microsoft-teams-with-teams-app-test-tool-and-dev-proxy.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,11 +14,11 @@ Many organizations are building custom copilots grounded in organizational data
14
14
15
15
The [ChatGPT + Enterprise data with Azure OpenAI and AI Search](https://github.com/Azure-Samples/azure-search-openai-demo) sample is an example of how to implement RAG on the Microsoft Cloud.
Employees use natural language to ask questions and receive answers based on data from a fictitious company called Contoso Electronics. Allowing them to ask questions about the benefits, internal policies, as well as job descriptions and roles.
20
20
21
-
21
+
22
22
23
23
Requests are sent to a back-end API when employees submit queries. Answers are returned in natural language along with document citations and follow-up questions in the response which are displayed in the user interface.
24
24
@@ -30,15 +30,15 @@ In the [ChatGPT + Enterprise data with Azure OpenAI and Cognitive Search in Micr
30
30
31
31
The bot sends requests to the same back-end API to return answers from the LLM.
32
32
33
-
33
+
34
34
35
35
The answers, along with document citations and action buttons, are returned in Adaptive Cards. In addition, follow-up questions are displayed as suggested actions.
36
36
37
37
## Removing platform dependencies
38
38
39
39
To run and develop the two sample projects that we've just seen, you need to setup and configure several cloud services, as well as have access to a Microsoft 365 tenant.
40
40
41
-
41
+
42
42
43
43
During development this can be inefficient, in both time and money. It takes time to get everything in place and each request you send to the LLM incurs a cost as does keeping these services up and running.
44
44
@@ -57,11 +57,11 @@ With Teams App Test Tool and Dev Proxy, you simulate only the dependencies you n
57
57
58
58
With Teams App Test Tool, you remove the dependency on a Microsoft 365 tenant, bot services, Microsoft Entra, and Dev Tunnels, whilst using real responses from the LLM.
59
59
60
-
60
+
61
61
62
62
By adding Dev Proxy, you remove the dependency on all cloud services and APIs, whilst using mocked responses to simulate the LLM response without changing any of your app code.
63
63
64
-
64
+
65
65
66
66
When you are ready to test against the live LLM, simply turn off Dev Proxy.
67
67
@@ -80,11 +80,11 @@ To run and test the bot locally using Teams App Test Tool and Dev Proxy:
80
80
81
81
In the Test Tool, select the "What is included in my Northwind heal…" button to send a message in the bot chat and issue a request to the back-end API.
82
82
83
-
83
+
84
84
85
85
In the Dev Proxy process output, you can see that the request to the back-end API is intercepted, a delay is added to simulate real-world latency, and the API response is mocked.
86
86
87
-
87
+
Copy file name to clipboardExpand all lines: src/content/blog/dev-proxy-v0-13-with-new-guidance-and-inspecting-web-requests.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,15 +26,15 @@ One of the frequent requests that we got from you was for Dev Proxy to show more
26
26
27
27
We're excited to introduce a new plugin that uses Chrome DevTools Protocol to let you explore requests and responses!
28
28
29
-
29
+
30
30
31
31
Using Chrome DevTools Protocol for inspecting requests intercepted by Dev Proxy is convenient for several reasons.
32
32
33
33
First of all, it's the same user interface that you already know from building web apps. Because Dev Proxy intercepts requests from all types of apps, you'll now be able to use the same set of tools for all API requests, including those issued by server-side code!
34
34
35
35
Dev Proxy is a command line tool, and its UI is limited by the textual nature of the terminal. Using Chrome DevTools Protocol takes Dev Proxy beyond the terminal and gives you a richer UX with the ability to filter requests and messages. You'll find it particularly convenient when using Dev Proxy with apps that issue many API requests. Using Chrome DevTools Protocol allows us to provide you with detailed information about all intercepted requests and responses without cluttering the terminal output.
36
36
37
-
37
+
38
38
39
39
Depending on your preference, you can use DevTools in Edge, Edge Dev channel or Chrome to inspect requests intercepted by Dev Proxy. Check it out and let us know how you like it!
40
40
@@ -44,7 +44,7 @@ Recently, we published [new guidance about Microsoft Search APIs](https://devblo
44
44
45
45
To help you understand where in your applications you're using OneDrive and SharePoint search APIs, and which you could update to use the recommended Microsoft Search APIs in Microsoft Graph, we introduce in this version of Dev Proxy new guidance plugin.
46
46
47
-
47
+
Copy file name to clipboardExpand all lines: src/content/blog/dev-proxy-v0-14-with-generating-openapi-specs-and-simulating-crud-apis.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ Spend more time on building your app and less on plumbing. Make your apps more r
24
24
25
25
Starting from this version, you can configure Dev Proxy to combine rate limiting with mock responses. This means, that when testing how your app handles rate limiting, you won't be calling your API and incurring unnecessary load. This combination is invaluable to verify if your rate limiting code is working as expected.
26
26
27
-
27
+
28
28
29
29
Learn more about [rate limiting](https://learn.microsoft.com/microsoft-cloud/dev/dev-proxy/concepts/what-is-rate-limiting).
30
30
@@ -34,15 +34,15 @@ OpenAPI specs allow you to benefit from the latest investments in the API space.
34
34
35
35
Dev Proxy now allows you to generate an OpenAPI spec based on the requests intercepted by the proxy. All you need to do is to start your app, have it call your API, and Dev Proxy will generate an OpenAPI spec for you from the requests it intercepted!
36
36
37
-
37
+
38
38
39
39
Learn more about [generating OpenAPI specs using Dev Proxy](https://learn.microsoft.com/microsoft-cloud/dev/dev-proxy/how-to/generate-openapi-spec).
40
40
41
41
## Simulate CRUD APIs for development
42
42
43
43
When building apps, you often interact with backend APIs. Sometimes, these APIs aren't yet available, or other teams are updating them to meet the latest requirements. To avoid waiting, you typically create a mock API that returns the data you need. While this approach unblocks you, it requires you to spend time on building an API that you eventually replace with the real one. To avoid wasting time, you can now use Dev Proxy to simulate a CRUD API and speed up development. All you need is a data set that you want to expose as an API and let Dev Proxy do the rest!
44
44
45
-
45
+
46
46
47
47
Learn more about [simulating CRUD APIs with Dev Proxy](https://learn.microsoft.com/microsoft-cloud/dev/dev-proxy/how-to/simulate-crud-api).
48
48
@@ -56,7 +56,7 @@ We regularly publish Dev Proxy presets which configure proxy for specific use ca
56
56
57
57
To make it easier for you to use these presets, you can now use the `devproxy preset get` command, to download and unzip the preset. All you need is the preset ID which you find on the preset's page in the sample gallery.
58
58
59
-
59
+
60
60
61
61
We hope that you find presets helpful and if you've got your own presets that you'd like to share with others, [submit them to the gallery](https://github.com/pnp/proxy-samples/blob/main/CONTRIBUTING.md)!
62
62
@@ -66,7 +66,7 @@ We've slightly changed the shape of mocks that we use in Dev Proxy. As we extend
66
66
67
67
The new structure defines a request and response object and a collection of header objects.
68
68
69
-
69
+
70
70
71
71
We've already updated all samples in the sample gallery to reflect this new structure. If you have your own mocks, you can convert them to the new format using a [script](https://github.com/waldekmastykarz/convert-devproxy-mocks).
72
72
@@ -78,7 +78,7 @@ Dev Proxy and its plugins use JSON files to define their configuration. To help
78
78
79
79
Recently, we've published [our new docs on Microsoft Learn](https://learn.microsoft.com/microsoft-cloud/dev/dev-proxy/overview). We've included the reference content we had on our GitHub Wiki and extended it with additional conceptual docs, all to help you build more robust apps and get more out of Dev Proxy. Check them out and let us know how we can make them better.
80
80
81
-
81
+
Copy file name to clipboardExpand all lines: src/content/blog/dev-proxy-v0-15-with-simulating-crud-apis-secured-with-microsoft-entra.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ In this version, we extend the CrudApiPlugin with support for simulating APIs se
29
29
30
30
When defining your CRUD API, you can choose which aspect of the access token you want to validate, like the audience, issuer, permissions or token lifetime, which is perfect for working with simulated access tokens. You can also choose to validate the token signature to ensure that the app is using a real token!
31
31
32
-
32
+
33
33
34
34
Learn more about [simulating CRUD APIs with Dev Proxy](https://learn.microsoft.com/microsoft-cloud/dev/dev-proxy/how-to/simulate-crud-api).
35
35
@@ -39,15 +39,15 @@ Many apps built on Microsoft cloud are secured with Microsoft Entra. Before you
39
39
40
40
In this version we introduce the new EntraMockResponsePlugin which allows you to simulate OAuth flows. After detecting an OAuth flow, the plugin updates auth codes and simulated access tokens so that they're accepted by Microsoft Identity libraries.
41
41
42
-
42
+
43
43
44
44
Stay tuned for more information and examples of using this plugin in the coming weeks.
45
45
46
46
## Improved monitoring URLs
47
47
48
48
To help you reuse your presets like generating OpenAPI specs, generating mocks, and execution summaries with different APIs, in this release we introduce a new option – urlsToWatch. This option enables you to provide URLs to watch from the command line. Simply use `-u` or `–urls-to-watch` and specify the URLs you want to monitor, without having to change your presets!
49
49
50
-
50
+
51
51
52
52
In this version, we also introduce support for monitoring URLs on a specific port only! This is invaluable if you build apps, for example using .NET Aspire, where you have several APIs running locally and want to watch requests to one of them. This feature gives you fine-grained control over URL watching for a more precise developer experience.
53
53
@@ -59,7 +59,7 @@ Plugins in Dev Proxy give you the ability configure it to your specific needs. W
59
59
60
60
Previously, we introduced the ability to add multiple instances of the same plugin. This is invaluable in cases where you want to, for example define multiple instances of CRUD APIs or define mocks which you can reuse across different presets. In this version, we improved this ability further by changing how plugins expose their command-line options, to avoid conflicts between the different instances.
61
61
62
-
62
+
Copy file name to clipboardExpand all lines: src/content/blog/dev-proxy-v0-16-with-simulated-handling-teams-admin-center-notifications-for-microsoft-graph-connectors.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,11 +25,11 @@ When deploying Graph connectors in your organization, you should consider packag
25
25
26
26
In this release of Dev Proxy, we're excited to ship the ability for you to simulate the Teams Admin Center notification for enabling and disabling Graph connectors. With the new feature, you can test your code locally end to end: from validating the token, to creating the connection with the ticket from the notification. And you can do all of this locally without deploying anything to Microsoft 365!
27
27
28
-
28
+
29
29
30
30
We not only simulate the Teams Admin Center notification. We also check if your code correctly implements the different steps, like properly responding to the notification request or including the ticket from the notification on the external connection creation request. If we see that one of the required steps is missing or implemented incorrectly, we'll warn you about it. This way you can find potential issues earlier and deploy your Graph connector with confidence.
31
31
32
-
32
+
33
33
34
34
Learn more about [simulating the Teams Admin Center notification for Graph connectors using Dev Proxy](https://learn.microsoft.com/microsoft-cloud/dev/dev-proxy/how-to/mock-teams-admin-center-notification-graph-connectors).
35
35
@@ -41,7 +41,7 @@ There are [several requirements](https://learn.microsoft.com/graph/connecting-ex
41
41
42
42
In this version of Dev Proxy, we're introducing a new Graph connector guidance plugin, which checks if your external connection is configured properly for use with Copilot for Microsoft 365. We start with validating if your external connection contains the required semantic labels. If it doesn't, we'll warn you and tell you which labels are missing.
43
43
44
-
44
+
45
45
46
46
We'll be expanding our checks in the future and hope that they'll help you deploy your Graph connectors with confidence.
47
47
@@ -53,7 +53,7 @@ Many applications these days rely on webhooks. Webhooks are a common way for sys
53
53
54
54
A common challenge for working with webhooks is simulating the change in the external system that triggers the webhook. In this version of Dev Proxy, we're introducing the MockRequestPlugin that allows you to send a preconfigured notification to your application with a single key press.
55
55
56
-
56
+
57
57
58
58
By itself, the MockRequestPlugin is a convenient method to send webhook notifications to your app. You can configure the different requests in an easy way in your project and share them with your colleagues. The plugin is also a powerful building block for implementing specialized plugins which encapsulate some additional logic and guidance, such as the one we've just mentioned that simulates Teams Admin Center notifications for Graph connectors.
59
59
@@ -65,15 +65,15 @@ Over the last year, Dev Proxy evolved into a powerful API simulator that support
65
65
66
66
To help you document your settings, we now introduce support for including comments in Dev Proxy configuration and plugin files.
67
67
68
-
68
+
69
69
70
70
We hope that it'll help you keep relevant notes next to your configuration so that you can easily share it with your colleagues. Oh, and if you happen to use VSCode, use .jsonc as the file extension for your config files. It'll keep VSCode from highlighting comments as errors.
71
71
72
72
## Improved UI
73
73
74
74
As we keep extending Dev Proxy with new features, we want to help you get the most out of it. In this version, we extend the UI with a list of hotkeys that you can use with Dev Proxy to invoke its different features.
75
75
76
-
76
+
0 commit comments